Retro Marimo Pair

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.

skills.sh installs: 5.2K
GitHub stars: 432
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add marimo-team/marimo-pair --skill retro-marimo-pair --agent claude-code

Installs into .claude/skills of the current project.

Files

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._code_mode — 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.