BC xiaozhi-teach-chinese-classical-guide
面向语文老师的文言文与古诗词教学设计工具。当老师说"这篇文言文怎么讲"、"古诗怎么上"、"学员读不懂文言文"、"实词虚词怎么教"、"文言翻译怎么带"、"古文背诵怎么落实"、"文言文主题怎么把握"、"诗词鉴赏怎么教"时，建议激活此SKILL。工作流：诵读正音 → 训诂（字词/句式/活用）→ 串讲 → 主题 → 文化背景与现代联结 → 班级古文积累记录。只输出教学框架与讨论问题，不逐字逐句串讲整篇、不提供完整现代文翻译、不代老师批改。现代文阅读教学转 xiaozhi-teach-chinese-reading-guide；作文教学转 xiaozhi-teach-chinese-writing-guide。
面向语文老师的文言文与古诗词教学设计工具。当老师说"这篇文言文怎么讲"、"古诗怎么上"、"学员读不懂文言文"、"实词虚词怎么教"、"文言翻译怎么带"、"古文背诵怎么落实"、"文言文主题怎么把握"、"诗词鉴赏怎么教"时，建议激活此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: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 304 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 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. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3371 tokens
- 100Running it twice. No mutating operations
- low 15 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 7 example trigger phrases
- +3Description length 304: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (27 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: 73.