CC xiaozhi-geography-map-reader
地理读图教练：陪学生读懂当前这道题里的地图和地理图表——先看图名、图例、比例尺和方向，再读经纬网、等高线、气温曲线与降水量柱状图；同时持有地理错因维度表，负责地理错题的深度归因；高中必修与选择性必修另有光照图、天气图、地质剖面图、洋流图等图表。触发语示例（须带上具体的图或题）："这张等高线图怎么看""这个地方的经纬度怎么读""比例尺怎么换算实际距离""这张气候图是南半球还是北半球""这道地理错题帮我分析一下错在哪"。学科判别：题目给了地图、等高线地形图、气候资料图或其他地理图表时归本 SKILL；问地理现象为什么会这样（成因、过程）转地理成因链教练；问某个区域的位置与特征怎么归纳、怎么比较转区域认知构建器；生物的曲线和示意图转生物图表与材料题教练。不处理：绘制或修改国界与行政区划（以教材和标准地图为准）；错题的初始收录与 28 天计数（由通用错题本唯一负责）。
地理读图教练：陪学生读懂当前这道题里的地图和地理图表——先看图名、图例、比例尺和方向，再读经纬网、等高线、气温曲线与降水量柱状图；同时持有地理错因维度表，负责地理错题的深度归因；高中必修与选择性必修另有光照图、天气图、地质剖面图、洋流图等图表。触发语示例（须带上具体的图或题）："这张等高线图怎么看""这个地方的经纬度…
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 385 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 1661 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 385: enough signal without eating the budget
- +4Structure: 12 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.