CC xiaozhi-math-word-problem-coach
初中到高中的数学应用题建模专项（高中覆盖必修与选择性必修）：只处理列不出式子这一步——初中是"文字→方程"，高中是"文字→函数、数列、三角形、统计或概率模型"。典型触发："这道数学应用题读了三遍不知道怎么列方程""不知道设什么为x""行程/工程/浓度/利润/增长率题总是列错式子""条件之间的关系理不清"。核心方法：数量关系三步提取法（识别量→用中文说关系→翻译成等式）。不处理：方程列出来之后的解方程与计算（转 xiaozhi-math-problem-solving-coach）、纯几何/代数运算题、错题收录与统计（转 xiaozhi-correction-notebook）、概念本身没建立（转 xiaozhi-math-concept-explainer）、物理的受力/电路应用题（转物理 SKILL）。
初中到高中的数学应用题建模专项（高中覆盖必修与选择性必修）：只处理列不出式子这一步——初中是"文字→方程"，高中是"文字→函数、数列、三角形、统计或概率模型"。典型触发："这道数学应用题读了三遍不知道怎么列方程""不知道设什么为x""行程/工程/浓度/利润/增长率题总是列错式子""条件之间的关系理不清"。核心方法：数…
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 357 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. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2010 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 357: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.