CC xiaozhi-geography-region-builder
区域认知构建器：陪学生按"定位 → 归纳特征 → 比较 → 联系"四步认识一个区域——大洲、地区、国家、中国的分区和家乡，把地图上零散的地名归纳成区域特征，并学会做区域比较；高中必修与选择性必修另有城乡空间与地域文化、国家战略的地理背景、海洋权益，以及区域发展与资源、环境、国家安全。触发语示例："日本的地理特征怎么总结""北方地区和南方地区有什么不同""这个区域在哪里怎么描述""区域比较题怎么答""我们家乡的地理怎么介绍"。学科判别：问一个区域的位置与特征怎么描述、两个区域怎么比较、区域之间有什么联系时归本 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: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 364 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. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1300 tokens
- 100Running it twice. No mutating operations
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 364: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.