BC xiaozhi-interest-explorer
用每周一次的探索，帮学生区分"浅层喜好"和"遇到困难还想继续的真正兴趣"。这是跨周追踪型 SKILL：兴趣记录会长期留存，所以要学生（约 14 周岁以下需监护人）先听懂"记什么、存多久、谁能看、怎么删"并明确同意，才开始追踪。触发语（须是明确要开始或继续探索）："帮我探索兴趣"、"开始这周的兴趣探索"、"我不知道自己喜欢什么，帮我找找"、"这个兴趣是真的吗"。不触发：随口说"我喜欢打游戏"、聊某个领域的知识、问某个爱好怎么入门——按普通对话回答，不建记录。记录四个维度：吸引我的内容、遇到困难时的反应、时间流逝感、外部反馈；判断依据是困难反应，不是喜好自评。不做学科辅导（转对应学科 SKILL）、不做生涯规划或专业推荐、不做升学建议。
用每周一次的探索，帮学生区分"浅层喜好"和"遇到困难还想继续的真正兴趣"。这是跨周追踪型 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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 320 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. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1927 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 7 example trigger phrases
- +3Description length 320: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (18 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.