Skip to content
SkillModel-led1,268 tokens in use

Retro

At the end of a session, list the friction, find its cause and build a checked fix into your agent setup, or conclude that no change is warranted.

680 stars on the repository MIT Licensephuryn/product-engineering · agent-harness/skills/retro
npx skills add phuryn/product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Retro costs

69tokens idle
1,268tokens in use
1,417tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure25/25
  • Examples6/15
  • Output15/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

Retro runs at the end of a session, started by name: /agent-harness:retro in Claude Code or $agent-harness:retro in Codex. It lists what slowed the session down, with the moment each item happened, finds the cause, and builds the fix into the setup.

The output is fixes made and checked, not a list of lessons. It prefers code (a script, hook or test), then an improved instruction or route, and adds a new rule only when the session gave it a receipt.

What You Get

  • A list of this session’s friction items, each tied to a moment
  • A cause for each item from five classes
  • Reversible repository fixes made and verified where they apply
  • Exact proposed text for changes outside the repository, such as user-level settings
  • A one-line report per item: incident, cause, fix, verification

Common Use Cases

  • After an agent ran tests against the wrong server twice
  • After the owner corrected the same mistake in one session
  • Recording a correction to an installed skill in the project’s own instructions
  • Deciding that a problem was a one-off and needs no rule

What Makes It Unique

Retro refuses to invent rules. An item with no moment behind it is dropped, a new rule needs a dated receipt, and code comes before prose. Corrections to a third-party skill go in the project’s own instructions, since an installed copy is overwritten by updates. It edits only reversible repository files and proposes global changes with exact text for the owner to apply.

Under The Hood

The skill is one instruction file with no scripts, and it runs only when you name it. The agent reviews the session, then edits repository files such as instruction files, routes, hooks and scripts, and checks them by running them in the shell, for example piping a sample payload into a hook. It leaves the user’s own settings and global instructions alone unless the owner says so, and it drafts an upstream issue only when asked.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers