retro-meta — Claude Code skill: what it does, how to install
Runs a deeper investigation across past retros and the current ax setup to surface fixes the regular heuristic missed. Triggered by phrases like "deep retro" or the /ax:retro-meta command.
AGPL-3.0 ★ 124 updated 2026-10-07
npx skills add Necmttn/ax --skill retro-meta -a claude-codeWhat retro-meta does
The skill hands reasoning to an external agent, Claude Code or Codex with a high thinking budget, while the ax CLI just gathers structured evidence and takes back any plan the user approves. It first checks already-accepted experiments that still lack a locked verdict, closing them with ax improve verdict or leaving them open when there isn't enough signal yet. It then works through the investigation prompts, reading skill files and the CLAUDE.md guidance files, and proposes findings for the user to confirm.
It needs axctl on PATH; if ax doctor fails, the skill stops and points to the DuckDB setup section in the docs. A useful run also needs at least three retros logged in the past month — fewer than that, and the skill suggests running ax:retro first to build up evidence.
It never writes a new skill file directly. Instead it drafts a plan under ~/.claude/plans/, asks for an explicit yes, and only then registers it through ax retro plan. Approved plans can optionally be handed to an internal scaffolding agent via ax improve accept --with-agent.
What it helps with
- spot ax setup improvements the standard heuristic doesn't surface
- resolve stalled experiment proposals and lock their verdicts
- check skill files and CLAUDE.md for duplicates before proposing changes
- draft a change plan backed by evidence from prior retros
- hand an approved plan off for automatic skill or hook scaffolding
Example prompts for the agent
- Run a deep retro on my ax setup
- /ax:retro-meta
- Investigate what's wrong with my agent setup
How to install retro-meta
1Skills CLI (Vercel)
npx skills add Necmttn/ax --skill retro-meta -a claude-code2Manually: put the files in place
~/.claude/skills/retro-meta/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/retro-meta/
1Skills CLI (Vercel)
npx skills add Necmttn/ax --skill retro-meta -a codex2Manually: put the files in place
.agents/skills/retro-meta/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Necmttn/ax --skill retro-meta -a cursor2Manually: put the files in place
.cursor/skills/retro-meta/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Necmttn/ax skills/retro-meta2Manually: put the files in place
.github/skills/retro-meta/SKILL.md1Skills CLI (Vercel)
npx skills add Necmttn/ax --skill retro-meta -a gemini-cli2Platform CLI
gemini skills install https://github.com/Necmttn/ax --path skills/retro-metaManually: put the files in place
.devin/skills/retro-meta/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Necmttn/ax --skill retro-meta -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about retro-meta
How do I install retro-meta in Claude Code?
Run npx skills add Necmttn/ax --skill retro-meta -a claude-code; the skill lands at ~/.claude/skills/retro-meta/SKILL.md.
What does retro-meta do?
It runs a deeper pass over accumulated retros and the current ax setup to find improvements the regular heuristic proposals miss, leaving the final call on any new plan to the user.
What does retro-meta require to run?
It needs axctl on PATH and at least three retros logged within the past 30 days, or it recommends running ax:retro first.