AB skill-sprint-pack-builder
Convert pasted lesson notes, workflow notes, upstream agent-skill ideas, or rough implementation notes into a public-safe ClawHub/Codex skill sprint pack with a 20-minute action, proof checklist, redaction checklist, Skool post, reusable skill card, next reps, and verification criteria.
As a process B 74/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
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 · 0
✓ No critical or high findings
Files scanned: 3. 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")
Process rating: all ten parameters 74/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 55 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1079 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +1No license
- +2Single-language instructions
- +3Description length 287: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 55 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.