skill-retro

You can use skill-retro to analyze recent skill execution logs, identify interruptions, and catalog self-correction events by parsing conversation history for tool calls. It targets invoked skills, ranks them by correction frequency, and generates concrete updates to their SKILL.md files.

The best way to update SKILL.md files automatically is to run a retroanalysis on the session. This process catalogs each correction event with its root cause and applies targeted edits, including script extraction suggestions, directly to the skill metadata.

To catalog correction events from conversation history, you need to parse the tool calls within the session logs. The analysis identifies the expected versus actual behavior, locates the correction event, and determines the root cause for each invoked skill.

Yes, you need read and write access to SKILL.md files. This access is required to parse conversation history for tool calls, generate concrete updates to the skill definitions, and verify the updated skill for consistency and validity after changes.

Yes, you can verify the consistency of a skill definition after applying automated metadata corrections. The analysis process validates the updated skill files after proposing and applying targeted edits to ensure future runs are smoother.

You should run a retroanalysis when developers iterate on Claude skills and want continuous improvement without manual review. It is ideal for spotting unnecessary pauses and self-corrections, then automatically refining the relevant skill's definition.