BD visual-interactive-courseware
可视化交互课件制作技能。当用户需要为课堂教学制作可视化、可交互的课件(HTML 单文件)时使用。触发场景:把教材知识点(如血液循环、四羊方尊、晨昏线、二分二至等)做成 SVG 演示 + 可交互的网页课件、知识卡和教师说明。适用学科:生物、历史、地理、物理、化学、数学等一切含结构、流程、现象的知识点。
可视化交互课件制作技能。当用户需要为课堂教学制作可视化、可交互的课件(HTML 单文件)时使用。触发场景:把教材知识点(如血液循环、四羊方尊、晨昏线、二分二至等)做成 SVG 演示 + 可交互的网页课件、知识卡和教师说明。适用学科:生物、历史、地理、物理、化学、数学等一切含结构、流程、现象的知识点。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 11. 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") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 43/100
- 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
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 62 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1857 tokens
- low The response is described with custom markup (3 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 150: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 62 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.