BF ppt-skill
触发关键词：演示、PPT、幻灯片、slides、presentation、keynote、deck、汇报、展示; 使用场景：用户需要生成演示文稿、汇报材料或教学幻灯片。
触发关键词：演示、PPT、幻灯片、slides、presentation、keynote、deck、汇报、展示; 使用场景：用户需要生成演示文稿、汇报材料或教学幻灯片。
As a process F 31/100 · Will not run — References files that are not bundled: revealjs/references/charts.md, revealjs/references/advanced-features.md, revealjs/references/base-styles.css
ProcedureSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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 · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5561 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: revealjs/references/charts.md - warning
missing-refreference to a missing file: revealjs/references/advanced-features.md - warning
missing-refreference to a missing file: revealjs/references/base-styles.css
Process rating: all ten parameters 31/100
Will not run. References files that are not bundled: revealjs/references/charts.md, revealjs/references/advanced-features.md, revealjs/references/base-styles.css
- 0Tools and files. 3 referenced file(s) missing: revealjs/references/charts.md, revealjs/references/advanced-features.md, revealjs/references/base-styles.css
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 70Execution cost. Instruction body is 5561 tokens
- 100Steps. 123 steps
- 100Consistency. Name and required fields are in place
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (67 tags): a typed call is more reliable
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)
- +3Description length 84: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -222 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 47 headings
- +3Step-by-step instructions: 123 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 41.