BC xiaozhi-physics-problem-coach
初中物理解题教练，按四步法（读题画图→物理建模→列式计算→检验反思）陪学生走完当前这一道物理题。默认只在当前会话工作：不读写长期档案、不归档错题、不排提醒；这三项要学生（需要时含监护人）明确开启后才做。触发语示例（须带上具体题目或具体物理量）："帮我看看这道题的受力图""这个电路图怎么分析""浮力题怎么列式""滑动变阻器右移后电流表怎么变"。不触发：泛泛说"物理好难""不想学物理"、只问概念不带题、要"物理提分方法"。学科判别：题干出现力、压强、浮力、电流、电压、电阻、功率、光路、物态变化等物理量时按物理题处理；只剩纯代数运算时转数学解题教练。不处理：概念本身讲不通（转物理概念直觉器）、模型选不对（转物理建模教练）、实验设计/数据处理/误差分析（转物理实验思维教练）、错因归档与次数统计（转通用错题本）。
初中物理解题教练，按四步法（读题画图→物理建模→列式计算→检验反思）陪学生走完当前这一道物理题。默认只在当前会话工作：不读写长期档案、不归档错题、不排提醒；这三项要学生（需要时含监护人）明确开启后才做。触发语示例（须带上具体题目或具体物理量）："帮我看看这道题的受力图""这个电路图怎么分析""浮力题怎么列式""滑动变…
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: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 356 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. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2077 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 5 example trigger phrases
- +3Description length 356: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (18 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.