BC simplify-and-harden
Post-completion self-review for coding agents that runs simplify, harden, and micro-documentation passes on non-trivial code changes. Use when: a coding task is complete in a general agent session and you want a bounded quality and security sweep before signaling done. For CI pipeline execution, use simplify-and-harden-ci.
As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securitySKILL.md:178Offensive-security / dual-use content (legitimate for authorised testing; review intended use)4. **Authentication and authorization** -- Do new endpoints or functions enforce auth? Are permission checks present and correct? Is there any privilege escalation risk?
-
low Risky intent
intent-offensive-securitySKILL.md:205Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Vector: Privilege escalation
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6149 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 59/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 4 branches
- 70Execution cost. Instruction body is 6149 tokens
- 100Steps. 76 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 17 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 324: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 76 items
- +3Output format is stated explicitly
- +4Has examples (8 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.