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
The user has asked for a **retrospective**. You are suggesting improvements to the coding agent's **environment** to improve future runs.
## Steps
1. Read [write-skills](../../authoring/write-skills/SKILL.md) for the writing style guide.
2. Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user doesn't specify a session, default to the current one.
3. Look for candidates for improvement in these categories.
- **Navigation**: how easy was it for the agent to find the right files? Are there hidden dependencies between files? Would a **navigation pointer** make it easier? _Use when_ the session took a long time to find a piece of information.
…
The line at the top of this page pins the label git:20261004.3e725c3, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4405 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
GitHub
dzhng/skills · 1,377 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v3mxmckbecc3gz4p
GET https://markdownregistry.com/api/v1/resolve?ref=dzhng/skills/retro
GET https://markdownregistry.com/api/v1/blob/f5520b9d164cbb86c3db36989cf5a9b792d9f777e15af175c529a93e05fbd64e
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.
dzhng/skills · skills/authoring/audit-agents/SKILL.md · Audit or rewrite AGENTS.md so it holds only lasting principles. Run it only when the user asks for it by name; never…
dzhng/skills · skills/authoring/eval-skills/SKILL.md · Eval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each…
dzhng/skills · skills/authoring/write-skills/SKILL.md · Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill…
dzhng/skills · skills/engineering/audit-choices/SKILL.md · Audit the choices an implementing agent made, not its diff — a pure decision audit that traces the session's history…
dzhng/skills · skills/engineering/audit-performance/SKILL.md · Audit and prioritize performance work through bounded-work and forward-progress checks. Use when asked to find…
dzhng/skills · skills/engineering/audit-tests/SKILL.md · Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests…
dzhng/skills · skills/engineering/auto-research/SKILL.md · Run fast, progressive experiments to map tunable parameters and their effects. Use when optimizing code, prompts…
dzhng/skills · skills/engineering/claude/SKILL.md · Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent…
dzhng/skills · skills/engineering/close-spec/SKILL.md · When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec)…
dzhng/skills · skills/engineering/code-review/SKILL.md · Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing…
dzhng/skills · skills/engineering/codex/SKILL.md · Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second…
dzhng/skills · skills/engineering/eli5/SKILL.md · Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works, and…
apmantza/pi-lens · .claude/skills/retro/SKILL.md · Run the pi-lens retrospective — turn a session, an incident, or a merged bug fix into environment changes (checks…
serejaris/personal-corp-os · templates/department/skills/retro/SKILL.md · Use when the user asks for "ретро", "обзор недели", or "что было за неделю" and the department needs a fact-based…
serejaris/personal-corp-os · skills/retro/SKILL.md · Ретро недели для штаба. Читает задачи всех отделов, собирает что сделано, что застряло и что повторяется, пишет…
