### Skill Improve
Works with
description: "Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change."
argument-hint: "[skill-name]"
allowed-tools: Read, Glob, Grep, Write, Bash
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskill-improveExecute the skills CLI command in your project's root directory to begin installation:
Fetches skill-improve from Donchitos/Claude-Code-Game-Studios and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate skill-improve. Access via /skill-improve in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
10.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
10.7K
stars
| name | skill-improve |
| description | "Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change." |
| argument-hint | "[skill-name]" |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Bash |
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-debt
Verify .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:
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 / worse
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:
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.Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
vercel-labs/skills
Registry listing for skill-improve matched our evaluation — installs cleanly and behaves as described in the markdown.
skill-improve reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: skill-improve is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: skill-improve is focused, and the summary matches what you get after install.
We added skill-improve from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
skill-improve reduced setup friction for our internal harness; good balance of opinion and flexibility.
skill-improve fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
skill-improve has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: skill-improve is the kind of skill you can hand to a new teammate without a long onboarding doc.
skill-improve has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 68