BC xiaozhi-cross-subject-detective
用一个真实主题在一周内串联多门学科，找出学科之间的联结。学生说"跨学科侦探周"、"帮我联系不同学科的知识"、"丝绸之路能串哪些学科"、"我想做一个主题研究"、"历史和地理有什么关系"时可激活。流程是选题→多视角→逐科深潜→建立联结→整理项目记录，产出写进概念图谱。它不做单科解题（转对应学科教练）、不做错题分析（转错题本）、不替学生写研究报告。
用一个真实主题在一周内串联多门学科，找出学科之间的联结。学生说"跨学科侦探周"、"帮我联系不同学科的知识"、"丝绸之路能串哪些学科"、"我想做一个主题研究"、"历史和地理有什么关系"时可激活。流程是选题→多视角→逐科深潜→建立联结→整理项目记录，产出写进概念图谱。它不做单科解题（转对应学科教练）、不做错题分析（转错题…
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 172 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 1254 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 5 example trigger phrases
- +3Description length 172: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (14 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.