streamlit-to-marimo

Convert Streamlit widgets and layout into marimo-compatible notebook constructs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/stellaromics/fast-bioinfo --skill streamlit-to-marimo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: streamlit-to-marimo
Source: https://github.com/stellaromics/fast-bioinfo/tree/main/.claude/agents/spatial-analysis/skills/streamlit-to-marimo
Command: npx skills add https://github.com/stellaromics/fast-bioinfo --skill streamlit-to-marimo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert Streamlit apps into marimo notebooks by translating widgets, layout, and state semantics to marimo-compatible constructs, enabling a more reactive, notebook-based workflow.

Core Features & Use Cases

  • Widget translation: map Streamlit inputs like sliders, text inputs, and selects to marimo equivalents with automatic value propagation.
  • Layout and state transfer: preserve the app's layout and interactivity in a single marimo notebook, preserving behavior and visuals.
  • Use Case: when migrating a rapid Streamlit prototype to a shareable marimo notebook for team collaboration and deployment.

Quick Start

Create a new marimo notebook by translating the Streamlit app's UI widgets and layout according to the streamlit-to-marimo reference.

Frequently Asked Questions about streamlit-to-marimo

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

FAQPage Schema
How do I convert a Streamlit app to a marimo notebook?

Migrating Streamlit apps to marimo notebooks requires translating Streamlit widgets, display elements, and layout into marimo-compatible constructs while preserving interactivity and state semantics for a reactive workflow.

How does widget translation work when migrating from Streamlit to marimo?

Widget translation maps Streamlit inputs like sliders, text inputs, and selects to marimo equivalents with automatic value propagation, ensuring the reactive cells maintain the original interactivity and state semantics.

Can I preserve Streamlit layout and state interactivity in a marimo notebook?

Yes, Streamlit to marimo migration preserves app layout and state interactivity by transferring visual structures and behaviors into a single reactive marimo notebook environment.

What is the best way to migrate a Streamlit prototype to a reactive notebook?

The best way to migrate a Streamlit prototype to a reactive notebook is to translate UI widgets and layout according to a streamlit-to-marimo reference, enabling team collaboration and deployment in marimo.

Do I need to manually map Streamlit elements to marimo equivalents?

No, an automated mapping engine translates Streamlit input widgets, display elements, and layout into marimo-compatible constructs, automatically propagating values to preserve behavior and visuals without manual mapping.

When should I migrate my Streamlit app to marimo?

You should migrate Streamlit apps to marimo when you need a more reactive, notebook-based workflow for team collaboration and deployment, moving away from Streamlit's traditional script execution model.