retro
Conduct a retrospective on a coding session.
Going through the checklist
What it can touch
No script files in its folder
Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.
How we know
Listed the 2 files in the skill’s folder on GitHub; none is a script or program.
No known risk pattern found
Launch7’s automated check read all 2 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.
How we know
Read 2026-10-10, commit 49dd158 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.
Recently maintained
Its repository has had changes recently.
How we know
Last push to mattpocock/skills: 2026-10-09 (1 days before the scan).
Read automatically from the skill’s own files on GitHub on 10 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check
Add it to your AI
Needs another skill. retro hands its work to writing-for-agents and does nothing on its own. The steps below add both.
Supported. Upload it once in Claude’s settings. Works on every plan, including Free.
Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.
In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.
Make sure code execution is switched on (Settings → Capabilities). Skills need it.
Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.
Add writing-for-agents the same way: retro hands its work to it and does nothing on its own.
How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end
More from mattpocock
All from this publisher →- code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating…
- codebase-design
Shared vocabulary for designing deep modules.
- diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions.
- domain-modeling
Build and sharpen a project's domain model.
- git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute.