BC xiaozhi-chinese-writing-coach
语文作文教练——不替学生写，只帮学生把自己的想法说出来、写下来。当学生说"帮我写作文"、"我的作文怎么改"、"帮我打开思路"、"检查我的作文提纲"、"记叙文写不具体"、"议论文论点怎么立"、发来作文题目或稿件时，建议激活此SKILL。5步流程（打开思路→检验逻辑→自己动笔→首读反馈→精准提升）＋写作风格档案、三文体策略、苏格拉底四连、AI辩论赛。不判定病句，只提示"可能有语病"并转 xiaozhi-chinese-grammar-tracker；阅读答题转 xiaozhi-chinese-reading-decoder。风格跟踪仅在学生同意后启用。
语文作文教练——不替学生写，只帮学生把自己的想法说出来、写下来。当学生说"帮我写作文"、"我的作文怎么改"、"帮我打开思路"、"检查我的作文提纲"、"记叙文写不具体"、"议论文论点怎么立"、发来作文题目或稿件时，建议激活此SKILL。5步流程（打开思路→检验逻辑→自己动笔→首读反馈→精准提升）＋写作风格档案、三文体策…
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: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 277 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. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2549 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 277: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (25 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.