BC xiaozhi-time-focus-coach
帮学生把学习时间记成账、找出黄金时段、用番茄钟稳住专注，并积累分心规律。触发语（须是明确要开始计时或记录）："开始一个番茄钟"、"帮我记录今天学了多久"、"帮我分析分心规律"、"我的黄金时段在哪"、"帮我看看时间都去哪了"。不触发：随口抱怨"我时间不够用""又拖延了""今天好困"——先按普通对话回应，要开始计时会另外问一句。它只处理"时间怎么用"，不处理学什么（转 30 天学习计划）、不分析错题（转错题本）、不验证理解（转费曼学习法）。长期记忆、提醒入队、跨 SKILL 共享三项默认关闭，各自要学生（约 14 周岁以下需监护人）明确同意后才启用。
帮学生把学习时间记成账、找出黄金时段、用番茄钟稳住专注，并积累分心规律。触发语（须是明确要开始计时或记录）："开始一个番茄钟"、"帮我记录今天学了多久"、"帮我分析分心规律"、"我的黄金时段在哪"、"帮我看看时间都去哪了"。不触发：随口抱怨"我时间不够用""又拖延了""今天好困"——先按普通对话回应，要开始计时会另外…
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 276 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. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2381 tokens
- 100Running it twice. No mutating operations
- low 11 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 7 example trigger phrases
- +3Description length 276: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (25 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.