BC thunder-update-model
Swap a built-in model in the catalog (retire one, add its replacement) end to end, from a fresh worktree to a verified branch ready for /thunderpush.
Swap a built-in model in the catalog (retire one, add its replacement) end to end, from a fresh worktree to a verified branch ready for /thunderpush.
As a process C 59/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.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-usereferences/swap-checklist.md:294Credential used in a network call (verify the destination is the intended service) (destination host is a configured variable; quoted — discussed, not commanded)`curl -H "Authorization: Bearer $MONITORING_TOKEN" "https://<api>/v1/health/models?model=<incoming-slug>"`
variable hostquoted
Files scanned: 2. 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") - note
edit-residuethe text marks something as outdated (lines 12, 63, 68, 70, 108, 118): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 59/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 22 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3415 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (5 tags): a typed call is more reliable
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 149: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.