BC xiaozhi-physics-concept-intuition
初中物理概念的直觉建立器，用生活类比、头脑实验、公式推导三种模型把概念从"背下来"变成"真的懂了"。触发语示例："压强到底是什么意思""电压和电流有什么区别""为什么物体会浮起来""惯性是不是一种力""内能和温度是一回事吗""凸透镜成像为什么会倒过来"。学科判别：问的是物理量、物理规律的含义与来由时归本 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 236 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 2302 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 7 example trigger phrases
- +3Description length 236: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (19 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.