BB ppt-rescue-kit
快速制作或补完可编辑 PPT,适用于工作汇报、项目提案、知识分享、 只有主题或尚未完成的演示稿;交付逐页文案、讲稿和引用,不只是大纲。 / Create or rescue an editable PowerPoint for work updates, proposals, or knowledge sharing from a topic or unfinished deck. Deliver slide copy, speaker notes, and sources retained in JishuDB. For report-led industry analysis decks, use end-to-end-industry-presentations instead.
快速制作或补完可编辑 PPT,适用于工作汇报、项目提案、知识分享、 只有主题或尚未完成的演示稿;交付逐页文案、讲稿和引用,不只是大纲。 / Create or rescue an editable PowerPoint for work updates, proposals, or knowledge…
As a process B 79/100 · Nearly there — no weak spots found
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/jishudb-setup/scripts/install-macos.sh:287High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)exactKeys(candidate.signing, ['certificateExpiresAt', 'cert…256', 'nativeFileCount'], 'candidate.signing');
quoted
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 79/100
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4904 tokens
- 100Steps. 41 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 347: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 41 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.