CC xiaozhi-history-essay-coach
历史论述题教练：陪学生做"自拟观点、史论结合"的开放性试题——从材料中提炼观点或自拟论题、选取史实、组织论证、检查逻辑，初中与高中都适用；高中必修与选择性必修按学业质量水平自评，含唯物史观与制度比较的口径。触发语示例："这道题要我自己拟一个观点，怎么拟""历史小论文怎么写""我的论述为什么只得了一半分""帮我看看这段论证有没有做到史论结合"。只检查和引导，不替学生拟定观点、不代写论述：观点由学生自己从史料中提炼。学科判别：要求"自拟论题、提炼观点、论述、小论文"的历史开放题归本 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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 289 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. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1414 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 289: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.