marimo

name	marimo
description	Reactive Python notebook system with cell reactivity, UI elements, SQL cells, plotting, and app deployment. DAAF's standard notebook format — stored as Git-friendly .py files, not .ipynb. For DAAF pipelines: Stage 9 notebooks compile existing executed scripts into cells verbatim as audit artifacts — no new analysis code or interactive widgets. Use when assembling Stage 9 research notebooks, building standalone interactive data apps, or converting Jupyter notebooks to marimo format.
metadata	{"audience":"research-coders","domain":"python-library","library-version":"0.19.x","skill-last-updated":"2026-03-28"}

marimo

marimo reactive Python notebook system for reproducible and interactive data work. Covers cell reactivity model, UI elements (sliders, dropdowns, tables, forms), SQL cells, DataFrame display, plotting integration, validation patterns for data pipelines, and deployment as apps, scripts, or WASM. Use when assembling Stage 9 research notebooks, developing reactive marimo notebooks, building interactive data apps, or converting Jupyter notebooks to marimo's Git-friendly .py format.

Comprehensive skill for building reactive Python notebooks with marimo. Use decision trees below to find the right guidance, then load detailed references.

What is Marimo?

marimo is an open-source reactive Python notebook that automatically keeps code and outputs consistent:

• Reactive: Run a cell, and dependent cells automatically re-run
• No hidden state: Delete a cell, its variables are scrubbed from memory
• Pure Python: Notebooks stored as .py files (Git-friendly)
• Interactive: UI elements sync with Python without callbacks
• Deployable: Run as scripts, deploy as web apps, export to WASM

How to Use This Skill

Reference File Structure

Each topic in ./references/ contains focused documentation:

File	Purpose	When to Read
quickstart.md	Installation, CLI, first notebook	Starting a new project
reactivity.md	Cell execution model, dataflow	Understanding marimo's reactive model
validation-patterns.md	Transform-validate patterns, checkpoints	REQUIRED for data analysis workflows
ui-elements.md	Interactive elements (mo.ui.*)	Adding interactivity
sql-data.md	SQL cells, dataframes, plotting	Working with data
outputs-layouts.md	Markdown, layouts, formatting	Styling outputs
apps-deployment.md	Apps, scripts, export, deploy	Sharing/deploying notebooks
gotchas.md	Common errors, best practices	Debugging issues

Reading Order

1. New to marimo? Start with quickstart.md then reactivity.md
2. Data analysis workflows? Read validation-patterns.md (REQUIRED for rigorous analysis)
3. Building features? Read the relevant topic file
4. Having issues? Check gotchas.md first

Related Skills

Load these skills together with marimo for comprehensive workflow support:

Always Load Together:

• data-scientist - Provides validation methodology and EDA principles that inform notebook structure
• polars - DataFrame operations for data transformations within notebooks

Load for Specific Features:

• plotnine - Static publication-quality plots (ggplot2 style)
• plotly - Interactive visualizations with hover/zoom

Prerequisite Knowledge: If new to marimo, first understand:

1. Python basics
2. DataFrame operations (polars or pandas)
3. Basic plotting concepts

---

CRITICAL: Stage 9 is Script COMPILATION, Not Dashboard Building

For data research workflows, the Stage 9 marimo notebook has ONE job: LITERALLY COPY script file contents into cells.

What Stage 9 IS

• A script viewer — Copy-paste scripts into marimo cells
• An audit tool — Display execution logs to prove what ran
• A file compiler — Read files, copy contents, format as notebook

What Stage 9 is NOT

• ❌ NOT a dashboard builder
• ❌ NOT an interactive analysis tool
• ❌ NOT a place for new aggregations or filters
• ❌ NOT a place for UI widgets (dropdowns, sliders, search)

Stage 9 Notebook Assembly

Stage 9 is handled by the notebook-assembler agent (see .claude/agents/notebook-assembler.md), which:

1. READS script files from scripts/stage{5,6,7,8}_*/
2. COPIES script code VERBATIM into code cells
3. COPIES execution logs VERBATIM into accordion cells
4. ADDS ONLY simple pl.read_parquet() + mo.ui.table() cells

ABSOLUTE PROHIBITIONS for Stage 9

The following are NEVER ALLOWED in Stage 9 notebooks:

Prohibited Element	Why
mo.ui.dropdown()	No dropdowns — not a dashboard
mo.ui.slider()	No sliders — not a dashboard
mo.ui.multiselect()	No multiselects — not a dashboard
mo.ui.text() for search	No search boxes — not a dashboard
.group_by() (new)	No new aggregations — copy script code only
.agg() (new)	No new aggregations — copy script code only
.pivot() (new)	No pivot tables — copy script code only
.filter() in data cells	No filtering — just load and display
.with_columns() in data cells	No transforms — just load and display
"Interactive Filters" section	Not a dashboard
"Data Explorer" section	Not a dashboard
"Institution Lookup" feature	Not a dashboard

The ONLY New Code Allowed

Data inspection cells may contain ONLY these two lines:

df = pl.read_parquet("path/to/file.parquet")
mo.ui.table(df.head(100))

No .filter(). No .with_columns(). No .select(). No aggregations. Just load and display.

Anti-Patterns (What BAD Output Looks Like)

# ❌ WRONG — This is new analysis code
tier_summary = risk_data.group_by("tier").agg(pl.len())

# ❌ WRONG — This is a dashboard widget
sector_dropdown = mo.ui.dropdown(options=["Public", "Private"])

# ❌ WRONG — This is a transformation when loading
df = pl.read_parquet("data.parquet").with_columns(pl.col("x") * 2)

# ❌ WRONG — This is filtering
filtered = df.filter(pl.col("state") == "VA")

# ✅ CORRECT — Verbatim script code in code cell
# SOURCE: scripts/stage5_fetch/01_fetch.py
import polars as pl
def _():
    # ... exact script contents (marimo cell wrapper) ...

# ✅ CORRECT — Simple load + display
df = pl.read_parquet("data/raw/file.parquet")
mo.ui.table(df.head(100))

See:

• .claude/agents/notebook-assembler.md for the complete behavioral protocol
• agent_reference/WORKFLOW_PHASE4_ANALYSIS.md Stage 9 for template

---

Quick Decision Trees

"I need to get started"

Getting started?
├─ Install marimo → ./references/quickstart.md
├─ Create first notebook → ./references/quickstart.md
├─ Understand how cells work → ./references/reactivity.md
└─ Run built-in tutorials → marimo tutorial intro

"I need interactivity"

Need interactive elements?
├─ Sliders, dropdowns, text inputs → ./references/ui-elements.md
├─ Tables with selection → ./references/ui-elements.md
├─ Forms with submit buttons → ./references/ui-elements.md
├─ Dynamic arrays of elements → ./references/ui-elements.md
├─ Charts with selection → ./references/sql-data.md (plotting section)
└─ Custom widgets (anywidget) → ./references/ui-elements.md

"I need to work with data"

Need data operations?
├─ Query dataframes with SQL → ./references/sql-data.md
├─ Connect to databases (Postgres, SQLite) → ./references/sql-data.md
├─ Display/filter dataframes → ./references/sql-data.md
├─ Create plots (Altair, Matplotlib, Plotly) → ./references/sql-data.md
└─ Interactive data exploration → ./references/sql-data.md

"I need to format output"

Need output formatting?
├─ Write markdown with Python values → ./references/outputs-layouts.md
├─ Arrange elements (hstack, vstack) → ./references/outputs-layouts.md
├─ Tabs, accordions, sidebars → ./references/outputs-layouts.md
├─ Progress bars, spinners → ./references/outputs-layouts.md
└─ Conditional output display → ./references/outputs-layouts.md

"I need to share/deploy"

Need to share or deploy?
├─ Run as read-only web app → ./references/apps-deployment.md
├─ Execute as Python script → ./references/apps-deployment.md
├─ Export to HTML/WASM → ./references/apps-deployment.md
├─ Deploy with Docker → ./references/apps-deployment.md
├─ Grid/slides layout → ./references/apps-deployment.md
└─ Convert from Jupyter → ./references/quickstart.md

"Something isn't working"

Having issues?
├─ "Multiple definitions" error → ./references/gotchas.md
├─ Cells not re-running as expected → ./references/reactivity.md
├─ UI element not updating → ./references/gotchas.md
├─ Cycle dependency error → ./references/gotchas.md
├─ Expensive cells running too often → ./references/gotchas.md
└─ Mutations not triggering updates → ./references/reactivity.md

Quick Reference

Essential CLI Commands

Command	Purpose
marimo edit	Launch notebook server
marimo edit notebook.py	Create/edit specific notebook
marimo run notebook.py	Run as read-only app
python notebook.py	Execute as script
marimo tutorial intro	Run interactive tutorial
marimo convert nb.ipynb -o nb.py	Convert other formats INTO marimo (inbound only)
marimo export html notebook.py	Export to HTML

Docker: When running in a container, add --host 0.0.0.0 --port 2718 --headless to run and edit commands.

Core marimo Library

Function	Purpose
mo.md("text")	Render markdown
mo.ui.slider(min, max)	Create slider
mo.ui.dropdown(options)	Create dropdown
mo.ui.table(data)	Interactive table
mo.hstack([...])	Horizontal layout
mo.vstack([...])	Vertical layout
mo.sql(f"SELECT ...")	SQL query
mo.stop(condition)	Conditionally stop execution

Topic Index

Topic	Reference File
Installation & Setup	./references/quickstart.md
CLI Commands	./references/quickstart.md
Reactive Execution	./references/reactivity.md
Cell Dataflow	./references/reactivity.md
Validation Patterns	./references/validation-patterns.md
Transform-Validate Pairs	./references/validation-patterns.md
Data Quality Checkpoints	./references/validation-patterns.md
Sliders & Inputs	./references/ui-elements.md
Tables & Forms	./references/ui-elements.md
SQL Cells	./references/sql-data.md
DataFrames	./references/sql-data.md
Plotting	./references/sql-data.md
Markdown	./references/outputs-layouts.md
Layouts	./references/outputs-layouts.md
Apps & Scripts	./references/apps-deployment.md
Export & Deploy	./references/apps-deployment.md
Common Errors	./references/gotchas.md
Best Practices	./references/gotchas.md

Citation

When this library is used as a primary analytical tool, include in the report's Software & Tools references:

marimo team. marimo: Reactive Python notebook [Computer software]. https://marimo.io/

Cite when: The analysis notebook is delivered as a marimo notebook (typically always true in DAAF pipelines). Do not cite when: marimo is not used for the analysis delivery format.