Skip to main content
skill CX Codex

tune — Claude Code skill for session retrospectives

tune reviews one coding session and records proposed agent-environment changes in ax. Use it to trace tool errors, wasted calls, and missing checks.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Necmttn/ax --skill tune -a claude-code
Open on GitHub

What tune does

The skill reads a session log and builds a ledger of tool calls, errors, denials, and retries. It then looks for possible changes to checks, guidance files, hooks, or information access. The ledger comes from python3 -I scripts/turns.py <log>; add --full to inspect individual commands.

Candidates are ranked by severity and filed in ax for later triage with /ax:retro. tune also prepares a brief for the session. It applies changes only when asked.

The session log must be accessible, and the ledger script needs Python 3. The skill scopes ingestion to the current session: bare ax ingest scans every transcript on the machine, so that command can use more resources.

What it helps with

  • trace the cause of failed or repeated tool calls
  • spot mistakes that an automated check could catch
  • separate mechanical coding rules from review guidance
  • file environment-change candidates in ax

Example prompts for the agent

  • Run a retrospective on this session with /ax:tune.
  • Review this session and file setup-change proposals in ax.
  • Find tool-use problems in this session and suggest checks.

How to install tune

1Skills CLI (Vercel)

npx skills add Necmttn/ax --skill tune -a claude-code

2Manually: put the files in place

~/.claude/skills/tune/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/tune/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about tune

How do I install tune in Claude Code?

Run npx skills add Necmttn/ax --skill tune -a claude-code. The skill is installed at ~/.claude/skills/tune/SKILL.md.

What does tune do?

It reviews one session log, identifies possible changes to the agent's environment, and files them as ax proposals. Use /ax:retro to triage those proposals.

Does tune require Python?

Yes. It runs python3 -I scripts/turns.py <log> to produce the tool-call ledger.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set11

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor