retro SKILL.md skillA
retro from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/retro@git:20261031.a30f018Pins git:20261031.a30f018 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/retro/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261031.a30f018, committed Oct 31, 2026
- Size
- 10,842 bytes
- Repository stars
- 30
- License
- MIT
Run a retro on one Claude Code session: read its transcript through a script that picks out the moments worth a finding (corrections, refusals, errors, retries, long searches, slow steps, stops for the user, blocks), turn them into one ranked list of setup changes, each with its evidence, what skipping it costs, a Checked or Hypothesis recommendation and where the change goes, and wait for the user's decision on each before giving the accepted ones a home: a config edit for the user, a ticket…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Retro A run that went badly once will go badly again unless something in the setup changes: the team config, a repo's checks or instructions, or roost itself. The retro reads what actually happened in a session, finds the moments that cost time or trust, and proposes the change that stops each one recurring, in the place that can enforce it. **First, load the team config with `roost-config`.** For now the retro covers one session: this one, or one the user names. It reads only that session's own transcript, never a subagent's. ## Rules - **Read-only until the user decides.** Before the checkpoint, never edit a file, the team config, a repo or roost, never file or change a ticket, and never message a session. - **The retro never runs a check itself.** A hypothesis's check is run by the user or a repo session, or ticketed. - **Every finding has evidence.** A finding whose problem isn't in the script's output, the transcript or the tracker isn't reported, however likely it seems. - **Quotes come only from the script's output,** which is already redacted. Never paste text from the transcript into a finding, a ticket or a handoff; cite the moment's session and time instead. …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/retro@sha256:d53094bede3006c9The line at the top of this page pins the label git:20261031.a30f018, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5no536xlji3jtow5)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 31, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10842 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5no536xlji3jtow5 GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/retro GET https://markdownregistry.com/api/v1/blob/d53094bede3006c93841be82bd1b10531a3a521ba6fea93ca822ef591118db1b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from beakpoint-insights/roost
Every file in beakpoint-insights/roost