BF svg2pptskill
Convert SVG content, Chinese character stroke order, province/country maps (Chinese, English or pinyin names like Anhui/China/USA/Japan), or SVG URLs into editable PowerPoint (.pptx) via the handbooks.cn SVG-to-PPT service. Requires an API key obtained from the handbooks homepage.
Convert SVG content, Chinese character stroke order, province/country maps (Chinese, English or pinyin names like Anhui/China/USA/Japan), or SVG URLs into…
As a process F 55/100 · Will not run — References files that are not bundled: {{download_url}}
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 4. 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
missing-refreference to a missing file: {{download_url}} - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 55/100
- 0Tools and files. 1 referenced file(s) missing: {{download_url}}
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (svg2pptskill) differs from the folder (svg2ppt-handbooks)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 15 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 1294 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (4 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)
- +2Single-language instructions
- +3Description length 281: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 15 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.