skill improve

Engineering Community

Skill notes

Phase 1: Parse Argument

Read the skill name from the first argument. If missing, output usage and stop: Verify .claude/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:

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:

Phase 3: Diagnose

Read the full skill file at .claude/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

Phase 4: Propose Fix

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.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Donchitos · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Parse Argument

Read the skill name from the first argument. If missing, output usage and stop: Verify `.claude/skills/[name]/SKILL.md` exists. If not, stop with: "Skill '[name]' not found."

02
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:

03
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:

04
Phase 3: Diagnose

Read the full skill file at `.claude/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

05
Phase 4: Propose Fix

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.

06
Phase 5: Write and Retest

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:

07
Phase 6: Verdict

Count 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:

08
Phase 7: Next Steps

Run `/skill-test static all` to find the next skill with failures. Run `/skill-improve [next-name]` to continue the loop on another skill. Run `/skill-test audit` to see overall coverage progress.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.