CC xiaozhi-history-timeline-builder
时空线索构建器：帮学生把史事放进正确的时间和空间——纵向理清阶段与因果，横向对照同一时期的中外史事，并练公元纪年、世纪、年代的换算和历史地图的识读；高中必修与选择性必修另有各专题的时空框架与时间轴骨架。触发语示例："帮我理一下近代史的时间线""公元前 221 年是几世纪""同一时期欧洲在发生什么""这几件事谁先谁后""这张历史地图怎么看"。学科判别：问时间先后、时段特征、同期中外对照、纪年换算、历史地图时归本 SKILL；给了史料要做概括、原因、影响的材料题转历史材料解析题教练；要"自拟观点、史论结合"的开放性论述转历史论述题教练。
时空线索构建器：帮学生把史事放进正确的时间和空间——纵向理清阶段与因果，横向对照同一时期的中外史事，并练公元纪年、世纪、年代的换算和历史地图的识读；高中必修与选择性必修另有各专题的时空框架与时间轴骨架。触发语示例："帮我理一下近代史的时间线""公元前 221…
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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 269 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. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1365 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 6 example trigger phrases
- +3Description length 269: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 24 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.