Retro — Coding Session Retrospective
Run a structured retrospective on a coding session to find environment improvements for future agent runs
- What
- Run a structured retrospective on a coding session to find environment improvements for future agent runs
- Cost
- Free
- Needs
- a coding agent session to look back on (works best with session logs on the machine). Optional: the companion `writing-for-agents` skill from the same repo.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a retrospective skill that turns a finished coding session into concrete environment improvements for the next one. It reads the session's primary sources (logs on the machine), then hunts for candidates across seven categories: navigation pain, automated checks (it reads the repo's own lint/typecheck/test scripts and CI first, and treats a repo with no guardrail as a finding in itself), coding standards, global AGENTS.md bloat, tool economy, no-op instructions, and information access. Candidates are presented in severity order, and the skill insists on a discipline: mechanical violations get deterministic checks (linter rules, pre-commit hooks, CI jobs), never another prose rule. By @mattpocock, listed here with credit to its creator. Honest caveats: it calls the companion `writing-for-agents` skill from the same repo — install it too or adapt; it references Claude Code conventions (`disable-model-invocation`, the Skill tool) but the content works for any agent. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a coding agent session to look back on (works best with session logs on the machine). Optional: the companion `writing-for-agents` skill from the same repo. Install "Retro — Coding Session Retrospective" for me. It runs a structured retrospective on a coding session and surfaces environment improvements (guardrails, standards, navigation) ranked by severity. Repository: https://github.com/mattpocock/skills/blob/main/skills/engineering/retro/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "mattpocock-retro". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.