Wasm Compatibility
ericmjl/llamabot
Check if a marimo notebook is compatible with WebAssembly (WASM) and report any issues.
Interactive development in marimo notebooks with validation loops.
$ npx skills add pymc-labs/CausalPy --skill working-with-marimo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pymc-labs/CausalPy working-with-marimo --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/working-with-marimo .claude/skills/working-with-marimo && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "working-with-marimo" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/working-with-marimo into .claude/skills/working-with-marimo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-marimo", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/working-with-marimoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pymc-labs/CausalPy --skill working-with-marimo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pymc-labs/CausalPy working-with-marimo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/working-with-marimo .agents/skills/working-with-marimo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "working-with-marimo" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/working-with-marimo into .agents/skills/working-with-marimo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-marimo", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pymc-labs/CausalPy --skill working-with-marimo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pymc-labs/CausalPy working-with-marimo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/working-with-marimo .cursor/skills/working-with-marimo && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "working-with-marimo" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/working-with-marimo into .cursor/skills/working-with-marimo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-marimo", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pymc-labs/CausalPy.git --path .agents/skills/working-with-marimo--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pymc-labs/CausalPy --skill working-with-marimo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pymc-labs/CausalPy working-with-marimo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/working-with-marimo .gemini/skills/working-with-marimo && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "working-with-marimo" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/working-with-marimo into .gemini/skills/working-with-marimo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-marimo", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pymc-labs/CausalPy working-with-marimoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pymc-labs/CausalPy --skill working-with-marimo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/working-with-marimo .github/skills/working-with-marimo && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "working-with-marimo" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/working-with-marimo into .github/skills/working-with-marimo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-marimo", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pymc-labs/CausalPy --skill working-with-marimo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pymc-labs/CausalPy working-with-marimo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/working-with-marimo .opencode/skills/working-with-marimo && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "working-with-marimo" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/working-with-marimo into .opencode/skills/working-with-marimo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "working-with-marimo", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
working-with-marimoInteractive development in marimo notebooks with validation loops.
Working With Marimo is an agent skill from pymc-labs/CausalPy. Interactive development in marimo notebooks with validation loops. Use for creating/editing marimo notebooks and verifying execution.
Its SKILL.md is about 360 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `reference/best_practices.md`).
It sits in Data & Analytics, covering Jupyter notebooks. It works with marimo and Model Context Protocol. The repository describes itself as: A Python package for causal inference in quasi-experimental settings. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit f17b30f. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Working With Marimo loads about 357 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 108 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from pymc-labs/CausalPy at commit f17b30f, republished under its Apache-2.0 licence (© pymc-labs). 108 words, ~357 tokens.
.claude/skills/working-with-marimo/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Follows a Plan-Execute-Verify loop to ensure notebook correctness.
Context & Plan:
mcp_marimo_get_active_notebooks (Find session IDs).mcp_marimo_get_lightweight_cell_map (See cell IDs/content).mcp_marimo_get_tables_and_variables (Inspect DataFrames/Variables).mcp_marimo_get_cell_runtime_data (Code, errors, local vars).Execute:
.py file directly using write or search_replace.@app.cell, no global state).Verify (CRITICAL):
mcp_marimo_lint_notebook (Static analysis).mcp_marimo_get_notebook_errors (Execution errors).mcp_marimo_get_cell_outputs (Visuals/Console).mo.sql for DuckDB queries.plt.gca() or return figure. No plt.show().See Best Practices for code formatting, reactivity rules, and UI element usage.
© pymc-labs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .agents/skills/working-with-marimo of pymc-labs/CausalPy.
Open the folder on GitHubat commit f17b30f
Working With Marimo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Working With Marimo this skillpymc-labs/CausalPy | 1.2k | — | ~357 | Automated safety check: Pass | Apache-2.0 | |
| Wasm Compatibilityericmjl/llamabot | 183 | 2 repos | ~1.6k | Automated safety check: Pass | None | |
| Marimo Paircosanlab/nltools | 131 | 1 repos | ~3k | Automated safety check: Pass | MIT | |
| Marimo Notebookcosanlab/nltools | 131 | 4 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Marimo Batchkoaning/gitcharts | 145 | 1 repos | ~819 | Automated safety check: Notes | None | |
| Marimo PairPhySpace/SimpleCADAPI | 142 | — | ~3k | Automated safety check: Pass | Apache-2.0 |
ericmjl/llamabot
Check if a marimo notebook is compatible with WebAssembly (WASM) and report any issues.
cosanlab/nltools
Work inside a running marimo notebook's kernel — execute code, create cells, and build a notebook as an artifact.
cosanlab/nltools
Write a marimo notebook in a Python file in the right format.
koaning/gitcharts
An opintionated skill to prepare a marimo notebook to make it ready for a scheduled run.
PhySpace/SimpleCADAPI
Drive a live marimo notebook as a workspace: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes.
marimo-team/marimo-lsp
Drive a live marimo notebook in VS Code as a workspace: run Python in the same kernel the user does, inspect and explore live notebook state and data, prototype and debug code, and commit durable…
pymc-labs/CausalPy
Load built-in CausalPy example datasets for demos, tutorials, tests, and quick causal-analysis prototypes.
pymc-labs/CausalPy
Review CausalPy pull requests end-to-end by classifying PR type, checking branch freshness, mergeability, remote CI, correctness, security, tests, docs, and maintainer concerns.
pymc-labs/CausalPy
Challenge causal claims through structured threat assessment, counterfactual reasoning, and CausalPy falsification checks.
pymc-labs/CausalPy
Performs placebo-in-time sensitivity analysis with hierarchical null model and optional Bayesian assurance.
pymc-labs/CausalPy
Detect, configure, and use the project's Python environment (uv by default, conda-compatible tool as a fallback).
pymc-labs/CausalPy
Explore unfamiliar APIs, libraries, or implementation behavior with minimal reproducible examples and documented findings.
Works with
Categories
Interactive development in marimo notebooks with validation loops. Working With Marimo is an agent skill from pymc-labs/CausalPy. Interactive development in marimo notebooks with validation loops.
Working With Marimo fits situations like: creating/editing marimo notebooks and verifying execution; tasks that involve Jupyter notebooks.
Run `npx skills add pymc-labs/CausalPy --skill working-with-marimo -a claude-code`. Or copy the skill folder (.agents/skills/working-with-marimo in pymc-labs/CausalPy) into .claude/skills/working-with-marimo in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pymc-labs/CausalPy --skill working-with-marimo -a codex`. Or copy the skill folder (.agents/skills/working-with-marimo in pymc-labs/CausalPy) into .agents/skills/working-with-marimo in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pymc-labs/CausalPy --skill working-with-marimo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/working-with-marimo, .gemini/skills/working-with-marimo, .github/skills/working-with-marimo and .opencode/skills/working-with-marimo in your project.
SKILL.md names no scripts, command-line tools or credentials: Working With Marimo is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Working With Marimo is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 357 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Working With Marimo: Wasm Compatibility (ericmjl/llamabot, 183 stars), Marimo Pair (cosanlab/nltools, 131 stars), Marimo Notebook (cosanlab/nltools, 131 stars) and Marimo Batch (koaning/gitcharts, 145 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
pymc-labs (a GitHub organization) maintains it in pymc-labs/CausalPy, which has 1,201 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.
Source: pymc-labs/CausalPy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.