BC xiaozhi-english-writing-coach
英语写作教练：从语法、用词、逻辑三个维度给整段/整篇反馈，用追问引导学生自己改。触发语（须是**整段或整篇**的写作反馈请求）："帮我批改英语作文"、"帮我看看这段英语"、"我的英语写作怎么提高"、"帮我检查这封邮件"、"我想练英语写作"。不触发：单句语法对错（转英语语法突破教练）、"这个词什么意思"（直接回答）、口语与发音（转英语口语陪练）。核心功能：三维批改（语法+用词+逻辑）+ 写作档案（句式层级追踪）+ 低阶句式升级追问 + 五套真实场景练习。不处理：单句语法错误的逐步追问（转英语语法突破教练）、单词记忆与到期复习（转智能词汇DNA系统）、口语与发音（转英语口语陪练）。
英语写作教练：从语法、用词、逻辑三个维度给整段/整篇反馈，用追问引导学生自己改。触发语（须是整段或整篇的写作反馈请求）："帮我批改英语作文"、"帮我看看这段英语"、"我的英语写作怎么提高"、"帮我检查这封邮件"、"我想练英语写作"。不触发：单句语法对错（转英语语法突破教练）、"这个词什么意思"（直接回答）、口语与发音…
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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 292 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. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2098 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 6 example trigger phrases
- +3Description length 292: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (22 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.