CC xiaozhi-biology-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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 298 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 1467 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 4 example trigger phrases
- +3Description length 298: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (3 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.