streamlit-to-marimo
Convert a Streamlit app to a marimo notebook
Install
With your agent
Install OMGSkills skill "marimo-team/skills:streamlit-to-marimo" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/marimo-team/skills /tmp/skills && ln -s /tmp/skills/skills/streamlit-to-marimo ~/.claude/skills/streamlit-to-marimo
From README
Converting Streamlit Apps to Marimo For general marimo notebook conventions (cell structure, PEP 723 metadata, output rendering, marimo check, variable naming, etc.), refer to the marimo-notebook skill. This skill focuses specifically on mapping Streamlit concepts to marimo equivalents. Steps Read the Streamlit app to understand its widgets, layout, and state management. Create a new marimo notebook following the marimo-notebook skill conventions. Add all dependencies the Streamlit app uses (pandas, plotly, altair, etc.) — but replace streamlit with marimo. You should not overwrite the original file. Map Streamlit components to marimo equivalents using the reference tables below. Key principles: UI elements are assigned to variables and their current value is accessed via .value. Cells that reference a UI element automatically re-run when the user interacts with it — no callbacks needed. Handle conceptual differences in execution model, state, and caching (see below).
