For marimo team members who want to turn a frustrating pairing session into actionable improvements. It walks you through identifying friction (user corrections, API workarounds, repeated attempts), diagnosing root causes (skill structure problems, missing docs, API ergonomics issues), and writing up a diagnosis without jumping straight to fixes. The goal is to file an issue or discussion, not ship a patch during the retro itself. Guards against premature edits to the marimo-pair skill repo and keeps you focused on what actually went wrong rather than what you think the solution is. Trigger it after a session that felt clunky or when you catch yourself wondering why something was harder than it should have been.
npx -y skills add marimo-team/marimo-pair --skill retro-marimo-pair --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills