CC xiaozhi-chemistry-micro-visualizer
用粒子图景讲清化学现象背后发生了什么：分子、原子、离子，化学变化的本质，质量守恒，溶解；高中延伸到必修与选择性必修（原子结构与化学键、反应中的能量、平衡的动态本质、电离与水解、分子的空间结构与晶体、有机物的结构）。触发语示例："为什么热胀冷缩""化学变化和物理变化在微观上有什么不同""为什么反应前后质量守恒""盐溶在水里去哪了""酸为什么都有相似的性质"。不触发：带具体数据要算的题（转化学解题教练）、化学式或方程式怎么写（转化学用语与方程式教练）、实验怎么做（转化学实验探究教练）。学科判别：问的是"粒子层面为什么"的化学问题归本 SKILL；问的是力、电、光等物理概念转物理概念直觉器。
用粒子图景讲清化学现象背后发生了什么：分子、原子、离子，化学变化的本质，质量守恒，溶解；高中延伸到必修与选择性必修（原子结构与化学键、反应中的能量、平衡的动态本质、电离与水解、分子的空间结构与晶体、有机物的结构）。触发语示例："为什么热胀冷缩""化学变化和物理变化在微观上有什么不同""为什么反应前后质量守恒""盐溶在…
As a process C 53/100 · Has gaps — 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.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 296 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "grade_bands" - note
frontmatter-keyunknown frontmatter key "depends_on" - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1202 tokens
- 100Running it twice. No mutating operations
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
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 296: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.