CC xiaozhi-chemistry-lab-coach
化学实验与探究教练：讲清装置为什么这样选、操作为什么是这个顺序、现象和结论怎么区分、检验与除杂怎么设计，覆盖初中 8 个学生必做实验与实验操作考试备考，高中延伸到必修与选择性必修的 18 个学生必做实验。触发语示例："制二氧化碳为什么不用稀硫酸""为什么要先检查装置气密性""这个实验的现象和结论怎么写""除去杂质选什么试剂""实验操作考试要注意什么"。不触发：纯计算题（转化学解题教练）、化学式与方程式写法（转化学用语与方程式教练）。学科判别：涉及化学仪器、装置、药品、操作、现象、检验与除杂的问题归本 SKILL；力学、电学实验转物理实验思维教练。不处理：在家自行操作的化学实验步骤（一律不给，见 shared/lab-safety.md）；错题归档与计数（转通用错题本）。
化学实验与探究教练：讲清装置为什么这样选、操作为什么是这个顺序、现象和结论怎么区分、检验与除杂怎么设计，覆盖初中 8 个学生必做实验与实验操作考试备考，高中延伸到必修与选择性必修的 18…
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: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 339 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. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1855 tokens
- 100Running it twice. No mutating operations
- low 12 top-level sections: this looks like several domains in one skill
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 5 example trigger phrases
- +3Description length 339: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (5 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.