skill-improve-59bae2 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skill-improve-59bae2 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Runs an improvement loop on a single skill: test → fix → retest → keep or revert.
Read the skill name from the first argument. If missing, output usage and stop:
Usage: /skill-improve [skill-name]
Example: /skill-improve tech-debtVerify .claude/skills/[name]/SKILL.md exists. If not, stop with: "Skill '[name]' not found."
Run /skill-test static [name] and record the baseline score:
Display to the user:
Static baseline: [N] failures, [M] warnings
Failing: Check 4 (no ask-before-write), Check 5 (no handoff)If baseline is 0 FAILs and 0 WARNs, note it and proceed to Phase 2b.
Look up the skill's category: field in CCGS Skill Testing Framework/catalog.yaml.
If no category: field is found, display: "Category: not yet assigned — skipping category checks." and skip to Phase 3.
If category is found, run /skill-test category [name] and record the category baseline:
Display to the user:
Category baseline: [N] failures, [M] warnings ([category] rubric)If BOTH static and category baselines are 0 FAILs and 0 WARNs, stop: "This skill already passes all static and category checks. No improvements needed."
Read the full skill file at .claude/skills/[name]/SKILL.md.
For each failing or warning static check, identify the exact gap:
context: fork set but fewer than 5 phases foundFor each failing or warning category check (if category was assigned in Phase 2b), identify the exact gap in the skill's text. For example:
PHASE-GATE director prompts
before each section write
Show the full combined diagnosis to the user before proposing any changes.
Write a targeted fix for each failure and warning. Show the proposed changes as clearly marked before/after blocks. Only change what is failing — do not rewrite sections that are passing.
Ask: "May I write this improved version to .claude/skills/[name]/SKILL.md?"
If the user says no, stop here.
Record the current content of the skill file (for revert if needed).
Write the improved skill to .claude/skills/[name]/SKILL.md.
Re-run /skill-test static [name] and record the new static score. If a category was assigned, also re-run /skill-test category [name] and record the new category score.
Display the comparison:
Static: Before [N] failures, [M] warnings → After [N'] failures, [M'] warnings
Category: Before [N] failures, [M] warnings → After [N'] failures, [M'] warnings (if applicable)
Combined change: improved / no change / worseCount the combined failure total: static FAILs + category FAILs + static WARNs + category WARNs.
If combined score improved (combined failure count is lower than baseline): Report: "Score improved. Changes kept." Show a summary of what was fixed in each dimension.
If combined score is the same or worse: Report: "Combined score did not improve." Show what changed and why it may not have helped. Ask: "May I revert .claude/skills/[name]/SKILL.md using git checkout?" If yes: run git checkout -- .claude/skills/[name]/SKILL.md
/skill-test static all to find the next skill with failures./skill-improve [next-name] to continue the loop on another skill./skill-test audit to see overall coverage progress.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.