tool-marimo

Convert notebooks into reactive marimo .py files with uv sandboxing.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/nishide-dev/claude-code-ml-research --skill tool-marimo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-marimo
Source: https://github.com/nishide-dev/claude-code-ml-research/tree/main/skills/tool-marimo
Command: npx skills add https://github.com/nishide-dev/claude-code-ml-research --skill tool-marimo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the reproducibility and collaboration pain of traditional notebook workflows by replacing hidden, order-dependent execution with deterministic reactive execution in pure Python files.

Core Features & Use Cases

  • Reactive notebooks as code: Re-runs the right parts automatically using a dependency DAG, preventing “run cells in the wrong order” issues.
  • Git-friendly .py format: Stores notebooks as plain Python scripts so diffs and reviews are clean and reliable.
  • uv-integrated, sandboxed execution: Uses PEP 723 metadata to manage dependencies consistently and reproducibly.
  • AI-optimized workflow: Makes notebook edits more dependable for LLM-assisted coding by keeping structure explicit and machine-readable.
  • Use cases: Parameterized data science/ML workflows, interactive dashboards, and shareable research apps (including WASM/serverless HTML exports).

Quick Start

Tell the AI: “Convert my existing notebook into a marimo .py file, add uv/PEP 723 dependencies, and refactor it into reactive cells with a simple UI control for a key parameter.”

Frequently Asked Questions about tool-marimo

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make Jupyter notebooks reproducible and prevent hidden state issues?

Reproducible notebooks eliminate hidden state by using reactive execution based on a dependency DAG, ensuring the correct cells re-run automatically and preventing order-dependent execution errors in data science workflows.

Can I convert existing notebooks into pure Python files for better version control?

Yes, you can convert existing notebooks into pure .py files that store content as plain Python scripts, enabling clean git diffs and reliable code reviews while maintaining interactive notebook functionality.

How does PEP 723 metadata help with reproducible sandboxed execution?

PEP 723 metadata enables reproducible sandboxed execution by defining dependencies consistently within the notebook file, allowing uv to manage and isolate the execution environment automatically.

What is the best way to optimize notebooks for AI-assisted coding?

AI-assisted coding is optimized by using pure Python notebook files with explicit, machine-readable structure and strict variable scoping, making LLM edits more dependable and preventing hidden state errors.

Can I deploy reactive notebooks as shareable web apps or HTML exports?

Yes, reactive notebooks can be deployed as parameterized dashboards, shareable research apps, or WASM serverless HTML exports, allowing interactive data science workflows to be distributed without backend infrastructure.

Do I need uv to manage dependencies for marimo reactive notebooks?

uv is used to manage dependencies consistently and reproducibly via PEP 723 metadata, ensuring the sandboxed execution environment is strictly controlled and portable across different machines.