CC xiaozhi-chemistry-error-dna
初中到高中（必修与选择性必修）的化学错题根因分析与档案，做化学六维（符号/微观/宏观概念/读题/实验/计算）子类型定位与弱项报告。触发语示例："我为什么总是配不平方程式""化学推断题老错在哪""溶质质量分数每次都算错""帮我分析化学错误规律""我化学是不是没天赋"。学科判别：错题涉及化学式、化学方程式、元素与化合价、酸碱盐、溶液、实验装置，或高中必修与选择性必修的相关内容（元素化合物、物质结构、反应原理、有机化学）时归本 SKILL；纯物理量计算转物理错误DNA。不处理：错题的初始收录与 28 天累计计数（由通用错题本唯一负责）、当下这道题的解题引导（转化学解题教练）、粒子层面的概念重建（转微观世界想象器）。
初中到高中（必修与选择性必修）的化学错题根因分析与档案，做化学六维（符号/微观/宏观概念/读题/实验/计算）子类型定位与弱项报告。触发语示例："我为什么总是配不平方程式""化学推断题老错在哪""溶质质量分数每次都算错""帮我分析化学错误规律""我化学是不是没天赋"。学科判别：错题涉及化学式、化学方程式、元素与化合价、…
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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 308 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 1992 tokens
- 100Running it twice. No mutating operations
- low 10 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 308: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.