Autonomous skill improvement for Claude Code, inspired by Karpathy's autoresearch.
Instead of optimizing a neural network overnight, it optimizes your Claude Code skills through parallel research agents and an iterative keep/discard improvement loop.
/auto-research my-skill-name
The command runs through 5 phases:
Reads your skill file, extracts metadata, and creates a backup.
Spawns 5 research agents simultaneously, each with a focused mission:
| Agent | Role | Method |
|---|---|---|
| Domain Expert | Finds best practices and conventions | Web search for guides, docs, style guides |
| Quality Auditor | Scores the skill on 7 dimensions | Structural analysis against quality rubric |
| Competitive Analyst | Finds how others solve similar problems | Searches cursor rules, AI prompts, cheatsheets |
| Gap Analyst | Identifies missing scenarios | User journey and edge case analysis |
| Tech Scout | Checks for outdated or deprecated content | Searches changelogs, breaking changes |
Combines all findings, de-duplicates, and ranks improvement proposals using:
Priority Score = Impact x Confidence / Complexity
Applies improvements one at a time (like autoresearch experiments):
- Apply a single, focused change
- Evaluate it (accuracy, clarity, value-add, simplicity)
- Keep if it improves the skill, Discard if it doesn't
- Repeat for the next proposal
Shows before/after quality scores, lists all kept/discarded experiments.
| autoresearch (ML) | auto-research (Skills) |
|---|---|
Modify train.py |
Modify SKILL.md |
| Train for 5 min on GPU | Research with 5 parallel agents |
Measure val_bpb (lower = better) |
Score on 7 quality dimensions (higher = better) |
| Keep if metric improves | Keep if quality improves |
git reset if worse |
Revert edit if worse |
results.tsv tracking |
Experiment log with keep/discard |
| Simplicity criterion | Same -- complex additions with marginal value get discarded |
The auditor agent scores skills on:
- Actionability -- Can Claude immediately act on the instructions?
- Clarity -- Is the language unambiguous?
- Completeness -- Does it cover the full workflow?
- Examples -- Are there enough concrete examples?
- Edge Cases -- Does it handle failure modes?
- Conciseness -- Every line earns its place?
- Trigger Accuracy -- Does the description match when it should activate?
Install directly from the Claude Code plugin directory:
/plugins
Search for auto-research and install it.
# In any Claude Code session:
/install-plugin https://github.com/gyoz-ai/auto-researchClone and symlink the skill:
git clone https://github.com/gyoz-ai/auto-research.git ~/auto-research
mkdir -p ~/.claude/skills/auto-research
ln -s ~/auto-research/skills/auto-research/SKILL.md ~/.claude/skills/auto-research/SKILL.mdOr copy directly:
mkdir -p ~/.claude/skills/auto-research
curl -o ~/.claude/skills/auto-research/SKILL.md \
https://raw.githubusercontent.com/gyoz-ai/auto-research/main/skills/auto-research/SKILL.md# In any Claude Code session:
# By skill name (looks in ~/.claude/skills/<name>/SKILL.md)
/auto-research my-skill
# By full path
/auto-research ~/.claude/skills/my-skill/SKILL.md
# By project-level path
/auto-research .claude/skills/my-skill/SKILL.mdThe command runs autonomously -- it won't ask for permission between experiments. When it's done, you can:
- Review the changes in detail
- Run another cycle for deeper improvements
- Revert all changes if you don't like them
- Claude Code CLI, desktop app, or IDE extension
- An existing skill to improve (in
~/.claude/skills/or.claude/skills/)
auto-research/
├── .claude-plugin/
│ └── plugin.json
├── skills/
│ └── auto-research/
│ └── SKILL.md
├── LICENSE
└── README.md
Methodology inspired by autoresearch by Andrej Karpathy -- the concept of autonomous, iterative experimentation with a keep/discard loop and simplicity criterion.
MIT