BC xiaozhi-teach-math-exam-designer
数学教师的测评设计：用双向细目表把"凭感觉出数学卷"变成可诊断的命题。仅在老师提出明确的数学命题任务时建议激活，例如"给八年级数学出一份单元测评""做一张数学双向细目表""算这次数学测评的逐题 P/D"；泛泛聊数学、问某题怎么解、问学生近况都不激活。只做四件事：命题蓝图与双向细目表、题目选编与版权标注、题目统计（逐题 P/D 与信度）、经老师逐条确认后的写回。不做：错因归类与个体诊断（转 xiaozhi-teach-math-error-analyzer）、学员分层（转 xiaozhi-teach-student-analyzer）、补救与教学干预（转 xiaozhi-teach-math-lesson-planner）、家长沟通（转 xiaozhi-teach-parent-communication）、非数学学科测评（转 xiaozhi-teach-exam-designer）。
数学教师的测评设计：用双向细目表把"凭感觉出数学卷"变成可诊断的命题。仅在老师提出明确的数学命题任务时建议激活，例如"给八年级数学出一份单元测评""做一张数学双向细目表""算这次数学测评的逐题…
As a process C 52/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: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 397 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 "id" - note
frontmatter-keyunknown frontmatter key "min_platform_version" - note
frontmatter-keyunknown frontmatter key "max_round_limit" - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary"
Process rating: all ten parameters 52/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
- 70Execution cost. Instruction body is 4691 tokens
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 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
- -213 emoji in the instructions: noise for the model
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 397: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (26 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.