jupyter-to-marimo
Skill4 starsChanged 3 days agoMITView on GitHub
Convert a Jupyter notebook (.ipynb) to a marimo notebook (.py).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- marimo-team/skillstheir own version, first seen Nov 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- marimo-team/skills★ 177same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository58 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- anywidget-generatorSkill
- brandkitSkill
- design-taste-frontendSkill
- diagram-designSkill
- docxSkill
- frontend-designSkill
- full-output-enforcementSkill
- gpt-tasteSkill
- grill-meSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- impeccableSkill
- implement-paper-autoSkill
- implement-paperSkill
- industrial-brutalist-uiSkill
- marimo-notebookSkill
- minimalist-uiSkill
- pdfSkill
- postrboardSkill
- pptxSkill
- redesign-existing-projectsSkill
- skill-creatorSkill
- stitch-design-tasteSkill
- streamlit-to-marimoSkill
- xlsxSkill
- brandkitSkill
- design-taste-frontendSkill
- full-output-enforcementSkill
- gpt-tasteSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- impeccableSkill
- industrial-brutalist-uiSkill
- minimalist-uiSkill
- redesign-existing-projectsSkill
- stitch-design-tasteSkill
- network-flowSkill
- create-lib-docsSkill
- artwallbgSkill
- commentdropSkill
- newsletter-aiSkill
- prodigySkill
- scrolls-explainerSkill
- scrolls-helpSkill
- scrolls-hideSkill
- scrolls-removeSkill
- scrolls-restoreSkill
- scrolls-setupSkill
- scrolls-unhideSkill
- scrolls-updateSkill
- stata-recipesSkill
- dynamic-promo-videoSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 2 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
IMPORTANT: When asked to translate a notebook, ALWAYS run uvx marimo convert <notebook.ipynb> -o <notebook.py> FIRST before reading any …
- Very specific: line 14
Run the marimo convert command via uvx so no install is needed:
- Very specific: line 32
Read the generated .py file and apply the following improvements:
- Distinctive: line 34
Ensure the script metadata block lists all required packages.
- Distinctive: line 36
Make sure the final expression of each cell is the value to render.
- Very specific: line 37
If the original notebook requires environment variables via an input, consider adding the EnvConfig widget from wigglystuff.
- Very specific: line 38
If the original notebook uses ipywidgets, see references/widgets.md for a full mapping of ipywidgets to marimo equivalents, including …
- Very specific: line 39
If the notebook contains LaTeX, see references/latex.md for how to port MathJax syntax to KaTeX (which marimo uses).
- Very specific: line 41
Run
marimo checkagain: after your edits to confirm nothing was broken.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Converting Jupyter Notebooks to Marimo
IMPORTANT: When asked to translate a notebook, ALWAYS run uvx marimo convert <notebook.ipynb> -o <notebook.py> FIRST before reading any files. This saves precious tokens - reading large notebooks can consume 30k+ tokens, while the converted .py file is much smaller and easier to work with.
Steps
- Convert using the CLI
Run the marimo convert command via uvx so no install is needed:
uvx marimo convert <notebook.ipynb> -o <notebook.py>This generates a marimo-compatible .py file from the Jupyter notebook.
- Run
marimo checkon the output
uvx marimo check <notebook.py>Fix any issues that are reported before continuing.
- Review and clean up the converted notebook
Read the generated .py file and apply the following improvements:
- Ensure the script metadata block lists all required packages. The converter may miss some.
- Drop leftover Jupyter artifacts like
display()calls, or%magiccommands that don't apply in marimo. - Make sure the final expression of each cell is the value to render. Indented or conditional expressions won't display.
- If the original notebook requires environment variables via an input, consider adding the
EnvConfigwidget from wigglystuff. Details can be found here. - If the original notebook uses ipywidgets, see
references/widgets.mdfor a full mapping of ipywidgets to marimo equivalents, including patterns for callbacks, linking, and anywidget integration. - If the notebook contains LaTeX, see
references/latex.mdfor how to port MathJax syntax to KaTeX (which marimo uses).
- Run
marimo checkagain after your edits to confirm nothing was broken.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

