agentleFS
sugatoraysugatoray/aiskills/.agents/skills/jupyter-to-marimo/SKILL.md

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

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
  1. Very specific:

    IMPORTANT: When asked to translate a notebook, ALWAYS run uvx marimo convert <notebook.ipynb> -o <notebook.py> FIRST before reading any …

    line 8
  2. Very specific:

    Run the marimo convert command via uvx so no install is needed:

    line 14
  3. Very specific:

    Read the generated .py file and apply the following improvements:

    line 32
  4. Distinctive:

    Ensure the script metadata block lists all required packages.

    line 34
  5. Distinctive:

    Make sure the final expression of each cell is the value to render.

    line 36
  6. Very specific:

    If the original notebook requires environment variables via an input, consider adding the EnvConfig widget from wigglystuff.

    line 37
  7. Very specific:

    If the original notebook uses ipywidgets, see references/widgets.md for a full mapping of ipywidgets to marimo equivalents, including …

    line 38
  8. Very specific:

    If the notebook contains LaTeX, see references/latex.md for how to port MathJax syntax to KaTeX (which marimo uses).

    line 39
  9. Very specific:

    Run marimo check again: after your edits to confirm nothing was broken.

    line 41

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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.

  1. Run marimo check on the output
uvx marimo check <notebook.py>

Fix any issues that are reported before continuing.

  1. 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 %magic commands 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 EnvConfig widget from wigglystuff. Details can be found here.
  • If the original notebook uses ipywidgets, see references/widgets.md for a full mapping of ipywidgets to marimo equivalents, including patterns for callbacks, linking, and anywidget integration.
  • If the notebook contains LaTeX, see references/latex.md for how to port MathJax syntax to KaTeX (which marimo uses).
  1. Run marimo check again after your edits to confirm nothing was broken.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.