AF html-ppt
HTML PPT Studio — author professional static HTML presentations in many styles, layouts, and animations, all driven by templates. Use when the user asks for a presentation, PPT, slides, keynote, deck, slideshow, "幻灯片", "演讲稿", "做一份 PPT", "做一份 slides", a reveal-style HTML deck, a 小红书 图文, or any kind of multi-slide pitch/report/sharing document that should look tasteful and be usable with keyboard navigation. Triggers include keywords like "presentation", "ppt", "slides", "deck", "keynote", "reveal", "slideshow", "幻灯片", "演讲稿", "分享稿", "小红书图文", "talk slides", "pitch deck", "tech sharing", "technical presentation".
As a process F 47/100 · Will not run — References files that are not bundled: assets/base.css, assets/themes/*.css, templates/full-decks/<name>/
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/base.css - warning
missing-refreference to a missing file: assets/themes/*.css - warning
missing-refreference to a missing file: templates/full-decks/<name>/ - warning
missing-refreference to a missing file: templates/single-page/*.html - warning
missing-refreference to a missing file: assets/animations/animations.css - warning
missing-refreference to a missing file: assets/animations/fx/*.js - warning
missing-refreference to a missing file: examples/my-talk/
Process rating: all ten parameters 47/100
- 0Tools and files. 7 referenced file(s) missing: assets/base.css, assets/themes/*.css, templates/full-decks/<name>/
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 35 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2373 tokens
- 100Running it twice. No mutating operations
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 11 example trigger phrases
- +3Description length 616: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.