CC xiaozhi-chemistry-notation-coach
化学用语专项教练：元素符号、化合价、化学式、化学方程式的书写与配平，初中起步，高中延伸到必修（原子结构示意图、电子式、有机反应式）与选择性必修（热化学方程式、电极反应式、电离与水解方程式、核外电子排布、结构简式与命名）。触发语示例："硫酸铝的化学式怎么写""这个方程式怎么配平""化合价总是记不住""2H 和 H2 的 2 有什么区别""什么时候标气体符号"。不触发：整道题的解题过程（转化学解题教练）、实验现象与操作（转化学实验探究教练）、说不清粒子层面发生了什么（转微观世界想象器）。学科判别：问的是化学式、化合价、方程式的写法与配平时归本 SKILL；只是题目里用到了方程式、真正卡在计算或推断时转化学解题教练。
化学用语专项教练：元素符号、化合价、化学式、化学方程式的书写与配平，初中起步，高中延伸到必修（原子结构示意图、电子式、有机反应式）与选择性必修（热化学方程式、电极反应式、电离与水解方程式、核外电子排布、结构简式与命名）。触发语示例："硫酸铝的化学式怎么写""这个方程式怎么配平""化合价总是记不住""2H 和 H2…
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 309 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. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1397 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 5 example trigger phrases
- +3Description length 309: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (1 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.