Awesome-omni-skill marimo
Guide for creating and working with marimo notebooks, the reactive Python notebook that stores as pure .py files. This skill should be used when creating, editing, running, or deploying marimo notebooks.
install
source · Clone the upstream repo
git clone https://github.com/diegosouzapw/awesome-omni-skill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/frontend/marimo" ~/.claude/skills/diegosouzapw-awesome-omni-skill-marimo && rm -rf "$T"
manifest:
skills/frontend/marimo/SKILL.mdsource content
marimo
Overview
marimo is an open-source reactive Python notebook that reinvents notebooks as reproducible, interactive, and shareable Python programs. Unlike traditional Jupyter notebooks, marimo notebooks:
- Store as pure
files (Git-friendly, no JSON).py - Execute reactively (like a spreadsheet)
- Run as scripts or deploy as web apps
- Prevent bugs through automatic dependency tracking
Installation
pip install marimo # Basic pip install marimo[recommended] # With extras pip install marimo[sql] # With SQL support marimo tutorial intro # Start tutorial
CLI Commands
# Edit marimo edit # New notebook marimo edit notebook.py # Edit existing marimo edit --watch --sandbox # Watch files, isolate deps # Run as app marimo run notebook.py # Read-only app marimo run notebook.py --watch # Auto-reload on changes # Run as script python notebook.py # Create from prompt marimo new "analyze sales data" # Convert marimo convert notebook.ipynb -o notebook.py # Export marimo export html notebook.py -o output.html marimo export html-wasm notebook.py -o output.html # Browser-executable
Key Concepts
Reactivity
Running a cell automatically runs all cells that depend on it. Execution order is determined by variable dependencies (DAG), not cell position.
Cell Rules
- Each global variable must be defined in exactly one cell
- Mutations like
aren't tracked; reassign insteadlist.append() - If mutating is needed, do it in the same cell as the declaration
File Format
Notebooks are pure Python files with marimo decorators:
import marimo app = marimo.App() @app.cell def _(): import marimo as mo return (mo,) @app.cell def _(mo): mo.md("# My Notebook") return ()
API Reference
Detailed documentation for each API is available in the
references/ directory. Consult these files for comprehensive examples and parameters.
Core
| API | Reference File | Description |
|---|---|---|
| Markdown | | for rich text, LaTeX, icons |
| HTML | | , , styling |
| Outputs | | , console redirection |
UI Elements
| API | Reference File | Description |
|---|---|---|
| Inputs | | Sliders, text, dropdowns, tables, forms, etc. |
| Layouts | | , , tabs, accordion, etc. |
| Media | | Images, audio, video, PDF, downloads |
| Plotting | | Altair, Plotly, matplotlib integration |
| Diagrams | | Mermaid diagrams |
| Status | | Progress bars, spinners |
Data
| API | Reference File | Description |
|---|---|---|
| SQL | | for database and DataFrame queries |
Advanced
| API | Reference File | Description |
|---|---|---|
| Control Flow | | , conditional execution |
| State | | for UI synchronization |
| Caching | | , |
| Query Params | | for URL state |
| CLI Args | | for script arguments |
| Watch | | for reactive file monitoring |
| App | | Embedding notebooks, |
| Cell | | Cross-notebook execution, testing |
Quick Examples
Basic UI
import marimo as mo slider = mo.ui.slider(0, 100, value=50, label="Threshold") slider # In another cell mo.md(f"Selected value: **{slider.value}**")
Interactive Table
table = mo.ui.table(df, selection="multi") table # In another cell selected = table.value # Selected rows as DataFrame
SQL Query
result = mo.sql(f"SELECT * FROM {df} WHERE value > {threshold.value}")
Conditional Execution
mo.stop(form.value is None, mo.md("Submit the form to continue")) # Rest of cell runs only after form submission
Running as Apps
marimo run notebook.py # Local app marimo export html-wasm notebook.py # Static WASM app
Layout options: Vertical (default), Grid (drag-drop in editor), Slides.
Best Practices
- Reactivity: Declare and mutate variables in the same cell
- Performance: Use
for expensive computations@mo.cache - UI Gating: Use
to prevent expensive ops until readymo.stop() - State: Avoid
unless synchronizing multiple UI elementsmo.state() - Organization: Cell position doesn't matter; organize for readability