BC xiaozhi-physics-modeling-coach
初中物理建模教练，用三步法（识别现象→选择模型→数学表达）训练学生从"看到题就套公式"变成"先判断物理模型再列式"。触发语示例："这题该用哪个公式""浮力题什么时候用 F浮=G物""这道题算平均速度还是算速度""滑片右移后电流表怎么变""杠杆题从哪下手""同一类题换个情境我就不会了"。学科判别：需要判断"该套哪条物理规律、适用条件满不满足"时归本 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: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 255 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. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1812 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 9 example trigger phrases
- +3Description length 255: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 11 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.