skill-retro

Analyze SKILL.md usage and draft diffs for friction points.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/RonanCodes/ronan-skills --skill skill-retro-ronancodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-retro
Source: https://github.com/RonanCodes/ronan-skills/tree/main/skills/skill-retro
Command: npx skills add https://github.com/RonanCodes/ronan-skills --skill skill-retro-ronancodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close the loop on skill usage. Read the session's invocations and SKILL.md references to surface friction, propose concrete edits, and commit improvements to the skill set.

Core Features & Use Cases

  • Enumerates skills touched in a session and sources feedback from conversation context and SKILL.md reads.
  • Proposes concrete edits to SKILL.md, drafts diffs, and can apply changes with a flag to commit them.
  • Generates a structured retro report guiding future improvements and knowledge updates.

Quick Start

Run /ro:skill-retro after a multi-skill task to generate a retro report and propose edits.

Frequently Asked Questions about skill-retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document friction points in skill usage after a multi-skill session?

To document friction points in skill usage, run a retro process that enumerates touched skills, sources conversation feedback, and generates a structured report with proposed SKILL.md edits to refine future invocations.

What is the best way to propose concrete edits to a SKILL.md file?

The best way to propose concrete edits to a SKILL.md file is to analyze session invocations, identify friction, and draft structured diffs for review before optionally committing the improvements to the skills directory.

How does a structured retro report help improve underperforming skills?

A structured retro report improves underperforming skills by analyzing session context and YAML frontmatter reads to surface friction points, guiding concrete documentation updates and knowledge improvements for future tasks.

Do I need access to the skills directory to run a documentation retro?

Yes, you need access to the skills directory to run a documentation retro, as the process requires reading SKILL.md files and YAML frontmatter to analyze friction and draft proposed diffs for review.

Can I automatically apply SKILL.md diffs generated from a session analysis?

Yes, you can automatically apply SKILL.md diffs generated from session analysis by using a specific flag to commit the proposed changes, closing the loop on skill usage and improving the skill set directly.