skill-improve

Skill Improve

Runs an improvement loop on a single skill: test → fix → retest → keep or revert.

---

Phase 1: Parse Argument

Read the skill name from the first argument. If missing, output usage and stop:

Usage: /skill-improve [skill-name]
Example: /skill-improve tech-debt

Verify .agents/skills/[name]/SKILL.md exists. If not, stop with: "Skill '[name]' not found."

---

Phase 2: Baseline Test

Run /skill-test static [name] and record the baseline score:

• Count of FAILs
• Count of WARNs
• Which specific checks failed (Check 1–7)

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.

Phase 2b: Category Baseline

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:

• Count of FAILs
• Count of WARNs
• Which specific category rubric metrics failed

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."

---

Phase 3: Diagnose

Read the full skill file at .agents/skills/[name]/SKILL.md.

For each failing or warning static check, identify the exact gap:

• Check 1 fail → which frontmatter field is missing
• Check 2 fail → how many phases found vs. minimum required
• Check 3 fail → no verdict keywords anywhere in the skill body
• Check 4 fail → Write or Edit in allowed-tools but no ask-before-write language
• Check 5 warn → no follow-up or next-step section at the end
• Check 6 warn → context: fork set but fewer than 5 phases found
• Check 7 warn → argument-hint is empty or doesn't match documented modes