streamlit-to-marimo

Translate Streamlit application code and UI components into reactive marimo notebooks.

3|Updated Apr 2, 2026

Search Tags:#refactoring #migration #streamlit #notebooks #data-science #marimo

Ready to run

npx skills add https://github.com/legout/pi-config --skill streamlit-to-marimo-legout

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: streamlit-to-marimo
Source: https://github.com/legout/pi-config/tree/main/installed-skills/streamlit-to-marimo
Command: npx skills add https://github.com/legout/pi-config --skill streamlit-to-marimo-legout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the friction of migrating legacy Streamlit applications to the reactive, notebook-based marimo framework by providing a structured mapping of UI components, state management, and execution models.

Core Features & Use Cases

Component Mapping: Provides a comprehensive reference table to translate Streamlit widgets like sliders, inputs, and buttons into their marimo equivalents.
Conceptual Translation: Guides the user through the shift from Streamlit's top-to-bottom rerun model to marimo's reactive cell DAG architecture.
Use Case: A data scientist wants to move an interactive dashboard from Streamlit to marimo to take advantage of better state management and local notebook execution without losing existing UI functionality.

Quick Start

Use the streamlit-to-marimo skill to convert the provided Streamlit application file into a functional marimo notebook.

Frequently Asked Questions about streamlit-to-marimo

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

FAQPage Schema

How do I migrate a Streamlit app to marimo?▼

To migrate a Streamlit app to marimo, translate the application code and UI components into reactive marimo notebook structures by mapping Streamlit widgets, layout containers, and caching decorators to their marimo counterparts.

What is the difference between Streamlit's rerun model and marimo's reactive execution?▼

Streamlit uses a top-to-bottom rerun model for execution, whereas marimo utilizes a reactive cell DAG architecture that manages dependencies locally, providing better state management for interactive tools.

Can I map Streamlit widgets like sliders and inputs directly to marimo?▼

Yes, you can map Streamlit widgets like sliders, inputs, and buttons directly to marimo equivalents using a comprehensive component reference table during the migration process.

Does migrating data dashboards from Streamlit to marimo require changing state management?▼

Yes, migrating data dashboards requires shifting state management to adhere to marimo's reactive execution model and cell-based dependency management instead of Streamlit's top-to-bottom reruns.

What are the limitations when converting Streamlit caching decorators to marimo?▼

The conversion requires strict adherence to marimo's reactive cell-based dependency management, meaning Streamlit caching decorators must be carefully mapped to marimo counterparts to avoid breaking the reactive execution flow.