CC xiaozhi-chinese-grammar-tracker
语文病句专项教练：按六类病句（中考、高考卷面常见的分类）判定，并在学生同意后建立语病档案；高中延伸到长句、复句与语境中的词语辨析、语体、简明连贯。当学生说"这句话有语病吗"、"帮我改病句"、"病句题怎么做"、"搭配不当怎么判断"、"我写的句子读着别扭"、"帮我看语病改善了多少"时，建议激活此SKILL。六类：语序不当 / 搭配不当 / 成分残缺或赘余 / 结构混乱 / 表意不明 / 不合逻辑。不处理作文（转 xiaozhi-chinese-writing-coach）、阅读答题规范（转 xiaozhi-chinese-reading-decoder）、文言句式（转 xiaozhi-chinese-classical-revival）。未获同意不建档、不跨SKILL共享。
语文病句专项教练：按六类病句（中考、高考卷面常见的分类）判定，并在学生同意后建立语病档案；高中延伸到长句、复句与语境中的词语辨析、语体、简明连贯。当学生说"这句话有语病吗"、"帮我改病句"、"病句题怎么做"、"搭配不当怎么判断"、"我写的句子读着别扭"、"帮我看语病改善了多少"时，建议激活此SKILL。六类：语序不当…
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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 339 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. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2317 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 339: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.