wasm-compatibility
Check if a marimo notebook is compatible with WebAssembly (WASM) and report any issues.
Install
With your agent
Install OMGSkills skill "marimo-team/skills:wasm-compatibility" 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/wasm-compatibility ~/.claude/skills/wasm-compatibilityFrom README
WASM Compatibility Checker for marimo Notebooks Check whether a marimo notebook can run in a WebAssembly (WASM) environment — the marimo playground, community cloud, or exported WASM HTML. Instructions Read the notebook Read the target notebook file. If the user doesn't specify one, ask which notebook to check. Run marimo's WASM lint rules marimo ships three lint rules that catch most WASM incompatibilities automatically. Run them first, and build the report from their output instead of re-deriving these checks by hand: MW001 incompatible-import — stdlib modules missing or non-functional in Pyodide (subprocess, pdb, dbm, resource, fcntl, termios, readline, curses, tkinter, pydecimal, test), plus multiprocessing exports and submodules that need native synchronization, shared memory, pipes, or process forking (Lock, Condition, Semaphore, Barrier, Manager, Pipe, RLock, sharedmemory, ForkContext/ForkProcess, ThreadPool, and others).
More from this repo
add-molab-badge
Used to add "Open in molab" badge(s) linking to marimo notebooks.
auto-paper-demo
Make a demo of a research paper in a marimo notebook fully automatically without extra user input.
implement-paper
Implement a research paper as an interactive marimo notebook together with the user.