marimo-team

Implement a research paper as an interactive marimo notebook together with the user. Start by understanding what the user wants to explore, fetch the paper via alphaxiv, then build a focused notebook.

Write a marimo notebook in a Python file in the right format.

An opintionated skill to prepare a marimo notebook to make it ready for a scheduled run.

Implement a research paper in a marimo notebook fully automatically without extra user input.

Make a demo of a research paper in a marimo notebook fully automatically without extra user input.

Generate anywidget components for marimo notebooks.

Convert a Jupyter notebook (.ipynb) to a marimo notebook (.py).

Add "Open in molab" badge(s) linking to marimo notebooks. Works with READMEs, docs, websites, or any markdown/HTML target.

Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.

Fill empty `description: ""` fields in `packages/llm-info/data/models.yml` by querying OpenRouter and provider documentation. Use when the user asks to populate model descriptions, enrich the model catalog, or backfill descriptions after running `pnpm sync-models`.

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.

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.

Drive a live marimo notebook in VS Code as a workspace: run Python in the same kernel the user does, inspect and explore live notebook state and data, prototype and debug code, and commit durable notebook changes (cells, values, packages). Use whenever working with a marimo notebook open in VS Code's notebook editor with an active kernel — running code, inspecting variables, exploring data, debugging, or editing and running cells — not only when explicitly "pairing" or starting a session.

Idiomatic Effect-TS patterns for the marimo-lsp extension. Use when writing or reviewing Effect code in `extension/src` — grounded in this repo's actual usage and citing into vendored Effect source at `repos/effect/`.