BF power-electronics
电力电子技术专家——四大变换 AC-DC/DC-AC/DC-DC/AC-AC。整流/PFC、SPWM/SVPWM/NPC三电平、Buck/Boost/Flyback/QR/LLC、相控/斩波。含 Simulink 仿真模板与 ClawHub 可发布。触发词:电力电子、NPC、QR反激、Simulink、PFC、SVPWM。
电力电子技术专家——四大变换 AC-DC/DC-AC/DC-DC/AC-AC。整流/PFC、SPWM/SVPWM/NPC三电平、Buck/Boost/Flyback/QR/LLC、相控/斩波。含 Simulink 仿真模板与 ClawHub…
As a process F 33/100 · Will not run — References files that are not bundled: references/four-conversions.md, references/formulas.md, references/topologies.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/four-conversions.md - warning
missing-refreference to a missing file: references/formulas.md - warning
missing-refreference to a missing file: references/topologies.md - warning
missing-refreference to a missing file: references/advanced.md - warning
missing-refreference to a missing file: references/examples.md - warning
missing-refreference to a missing file: references/simulink-templates.md - warning
missing-refreference to a missing file: PUBLISHING.md - warning
missing-refreference to a missing file: scripts/power_calc.py - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "config"
Process rating: all ten parameters 33/100
- 0Tools and files. 8 referenced file(s) missing: references/four-conversions.md, references/formulas.md, references/topologies.md
- 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
- 30Running it twice. 4 mutating operations with no state check
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 536 tokens
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 162: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.