CC xiaozhi-geography-causal-chain
地理成因链教练：陪学生把"为什么"连成一条完整的链——从纬度、海陆位置、地形或人类活动这些起点出发，一环一环连到要解释的现象，覆盖昼夜交替与四季变化、气候成因、地势对河流的影响、板块运动和人地关系；高中必修与选择性必修另有大气受热过程与热力环流、水循环、自然灾害、城镇化与区位因素，以及地球运动的地理意义、天气系统、气压带风带、洋流和碳排放的影响。触发语示例："为什么会有四季""这里为什么降水多""地势西高东低有什么影响""这道原因题我总答不全""过度放牧为什么会导致荒漠化"。学科判别：问地理现象的成因、过程和影响，或原因类设问答不全时归本 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 351 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. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1179 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 5 example trigger phrases
- +3Description length 351: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.