BC xiaozhi-teach-chinese-writing-guide
面向语文老师的作文教学与批改标准工具。当老师说"这周写什么作文"、"作文怎么批改"、"作文讲评怎么上"、"作文怎么定档打分"、"学员的写作风格怎么看"、"写作任务怎么设计"时，建议激活此SKILL。工作流：写作任务设计（命题/半命题/情境）→ 过程引导（构思/起草/修改）→ 等级批改（一至四类文 × 内容/结构/语言/书写）→ 三维观察诊断 → 讲评设计 → 班级写作力记录。只输出批改标准与讲评设计，不代老师逐篇精批、不为学员代写作文。阅读教学转 xiaozhi-teach-chinese-reading-guide；文言文教学转 xiaozhi-teach-chinese-classical-guide。
面向语文老师的作文教学与批改标准工具。当老师说"这周写什么作文"、"作文怎么批改"、"作文讲评怎么上"、"作文怎么定档打分"、"学员的写作风格怎么看"、"写作任务怎么设计"时，建议激活此SKILL。工作流：写作任务设计（命题/半命题/情境）→ 过程引导（构思/起草/修改）→ 等级批改（一至四类文 ×…
As a process C 51/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 307 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 51/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
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3073 tokens
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 6 example trigger phrases
- +3Description length 307: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (22 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.