# Build Reactive Marimo Notebooks

Reactive Python notebooks can be hard to structure and debug. This skill guides marimo cells, UI elements, data workflows, and app deployment.

## Install

```bash
npx skillstore add codingkaiser/marimo-development
```

## Metadata

- Status: approved
- Slug: codingkaiser-marimo-development
- Skillstore revision: r1
- Version status: missing
- Tree hash: 62c28f514c81c0612e477295333158300dd4c4122af045ed7eed4bd2dadf71e5
- Author: CodingKaiser
- GitHub username: CodingKaiser
- License: MIT
- Repository: https://github.com/CodingKaiser/claude-kaiser-skills/tree/main/marimo-development
- Ref: 02f077c174c5335e2f5d02ca15e77b70d9543e58
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, scripts, external\_commands, network, env\_access
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/codingkaiser-marimo-development
- Manifest: https://skillstore.pages.dev/api/skills/codingkaiser-marimo-development/manifest

## Capabilities

- Explains marimo cell structure and reactive execution rules.
- Guides creation of sliders, tables, forms, chat inputs, and custom widgets.
- Shows patterns for pandas, Polars, DuckDB, SQL, and plotting workflows.
- Helps debug dependency cycles, stale UI values, and notebook execution issues.
- Supports notebook-to-app layouts, script execution, and deployment guidance.
- Points to focused reference files for marimo APIs and common recipes.

## Use Cases

- Create an interactive analysis notebook: Build a marimo notebook with clean cells, reactive controls, data tables, and charts.
- Convert a prototype into a data app: Turn notebook outputs into an app layout with forms, tabs, sidebars, and deployment commands.
- Debug reactive notebook behavior: Diagnose stale values, circular dependencies, redeclared variables, and expensive reruns.

## Prompt Templates

### Start a notebook

```
Create a marimo notebook for exploring a CSV file. Include clear cells for imports, loading, filters, and charts.
```

### Add interactive controls

```
Add marimo UI controls to this notebook. Use reactive values correctly and keep each widget separate from cells that read its value.
```

### Debug notebook reactivity

```
Review this marimo notebook for reactivity problems. Identify redeclarations, cycles, mutation issues, and cells that should be stopped or cached.
```

### Design a deployed app

```
Design a marimo app from this analysis workflow. Include layout choices, SQL or dataframe patterns, deployment steps, and validation checks.
```

## Limitations

- It does not install marimo or project dependencies by itself.
- Generated notebook code still needs local testing with the user data.
- Private database, API, and deployment settings require user-provided credentials.
- Future marimo API changes may require checking current upstream documentation.

## Best Practices

- Keep widget definitions separate from cells that read widget values.
- Use descriptive global names and local underscore variables to avoid collisions.
- Test generated notebooks with marimo checks before sharing or deployment.

## Anti Patterns

- Do not redeclare the same variable across multiple marimo cells.
- Do not rely on hidden execution order from Jupyter notebooks.
- Do not hardcode production secrets or database credentials in notebooks.

## Security Audit

- Audited at: 2026-07-05T06:33:55.684\+00:00
- Summary: All static findings were adjudicated as false positives caused by Markdown documentation links, placeholder credentials, public example URLs, and visible user-run examples. Reviewed context did not show prompt injection, covert exfiltration, malicious command construction, or executable installer behavior.

## Stats

- Views: 944
- Downloads: 9
- Favorites: 0
- Popularity score: 0