marimo-pair
Drive a live marimo notebook as a workspace: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes. Use when the user wants to start a marimo notebook or pair on an active marimo session.
Install
With your agent
Install OMGSkills skill "marimo-team/marimo-pair" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/marimo-team/marimo-pair /tmp/marimo-pair && ln -s /tmp/marimo-pair/skills/marimo-pair ~/.claude/skills/marimo-pairFrom README
Required first kernel command Start every code-mode session with this dedicated command: Follow this order for each kernel, including read-only tasks: Run the inspection command once. Wait for successful help(cm) output. Then use cm.getcontext() or another cm API in a later call. Do not run task-specific cm code before the inspection command succeeds. Connect to a Notebook Use the bundled execute-code.sh from the reported skill directory or MCP (executecode(...)) to run Python in a live marimo kernel. execute-code.sh always takes --url. If the user provides a notebook URL, run the required inspection against it directly: After that command succeeds, pass task code with -c CODE, - for stdin, or a file path: If the user gives no URL, find or start a notebook. Look for a running server with bash /absolute/path/to/marimo-pair/scripts/discover-servers.sh, MCP listsessions(), or local process context, and pass the url it reports to --url.