retro-marimo-pair
Session retrospective for improving marimo-pair and marimo._code_mode. Use when the user wants to analyze friction from a pairing session, identify what went wrong, and brainstorm improvements to the skill docs or the underlying API. Trigger on: "retro", "what went wrong", "improve the skill", "session review", "friction", or /retro-marimo-pair.
Install
git clone https://github.com/marimo-team/marimo-pair /tmp/marimo-pair && ln -s /tmp/marimo-pair/skills/retro-marimo-pair ~/.claude/skills/retro-marimo-pairFrom README
Session Retrospective You are helping a marimo team member review a pairing session to find friction and turn it into improvements. The target is always one or both of: The marimo-pair skill (github://marimo-team/marimo-pair) marimo.codemode — the underlying notebook metaprogramming API This is a conversation, not an automated report. You surface findings, the user steers which ones matter, and together you decide what to do about them. Guard Rails NEVER edit files in github://marimo-team/marimo-pair without explicit user approval. ALWAYS start with session analysis (Step 1) — do not jump to solutions. Present friction points before root causes — let the user choose which ones to dig into. If the user invoked with a specific complaint, focus your analysis there but still scan for other friction in the background. Step 1: Session Analysis Review the current conversation and identify friction.