CC xiaozhi-bridge-planner
初高衔接规划：中考结束到高一上学期，诊断语文、数学、物理、化学、英语、生物、地理、历史各自的衔接缺口，排出暑假与高一开学头几周的衔接计划，再把具体内容交给对应的学科技能。触发语示例："中考完了，暑假怎么预习高中""高一物理听说很难，现在该准备什么""初中化学没学扎实，上高中会不会跟不上""初二就考完地理了，高一还要学地理吗""开学一个月了，高中数学完全跟不上，怎么补"。它只管"先补什么、后预习什么、每周怎么排"：不讲具体题目（转对应学科技能），不做通用学习计划（转 30天学习计划制定师），不发提醒（转 IM 智能提醒）。读学习档案与把任务放进提醒队列都需要学生明确同意后才做，默认都关着。
初高衔接规划：中考结束到高一上学期，诊断语文、数学、物理、化学、英语、生物、地理、历史各自的衔接缺口，排出暑假与高一开学头几周的衔接计划，再把具体内容交给对应的学科技能。触发语示例："中考完了，暑假怎么预习高中""高一物理听说很难，现在该准备什么""初中化学没学扎实，上高中会不会跟不上""初二就考完地理了，高一还要学…
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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 297 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. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1292 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 297: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.