Wasm Compatibility
ericmjl/llamabot
Check if a marimo notebook is compatible with WebAssembly (WASM) and report any issues.
Implement a research paper as an interactive marimo notebook together with the user.
Install Implement Paper
$ npx skills add marimo-team/skills --skill implement-paper -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install marimo-team/skills implement-paper --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/marimo-team/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implement-paper .claude/skills/implement-paper && 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 "implement-paper" agent skill from https://github.com/marimo-team/skills/tree/main/skills/implement-paper into .claude/skills/implement-paper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-paper", 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/marimo-team/skills/tree/main/skills/implement-paperType 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 marimo-team/skills --skill implement-paper -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install marimo-team/skills implement-paper --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marimo-team/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/implement-paper .agents/skills/implement-paper && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implement-paper" agent skill from https://github.com/marimo-team/skills/tree/main/skills/implement-paper into .agents/skills/implement-paper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-paper", 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 marimo-team/skills --skill implement-paper -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install marimo-team/skills implement-paper --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marimo-team/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/implement-paper .cursor/skills/implement-paper && 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 "implement-paper" agent skill from https://github.com/marimo-team/skills/tree/main/skills/implement-paper into .cursor/skills/implement-paper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-paper", 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/marimo-team/skills.git --path skills/implement-paper--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 marimo-team/skills --skill implement-paper -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install marimo-team/skills implement-paper --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marimo-team/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/implement-paper .gemini/skills/implement-paper && 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 "implement-paper" agent skill from https://github.com/marimo-team/skills/tree/main/skills/implement-paper into .gemini/skills/implement-paper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-paper", 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 marimo-team/skills implement-paperInstalls 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 marimo-team/skills --skill implement-paper -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/marimo-team/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/implement-paper .github/skills/implement-paper && 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 "implement-paper" agent skill from https://github.com/marimo-team/skills/tree/main/skills/implement-paper into .github/skills/implement-paper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-paper", 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 marimo-team/skills --skill implement-paper -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install marimo-team/skills implement-paper --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/marimo-team/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/implement-paper .opencode/skills/implement-paper && 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 "implement-paper" agent skill from https://github.com/marimo-team/skills/tree/main/skills/implement-paper into .opencode/skills/implement-paper/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implement-paper", 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.
Facts
- Skill name
implement-paper- GitHub stars
- 174
- Token cost
- ~1.1k tokens
- SKILL.md length
- 571 words
- Files
- 3 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implement a research paper as an interactive marimo notebook together with the user.
- Works in 4 steps: Understand what the user wants → Fetch the paper → Plan the notebook → …
- Tasks that involve Jupyter notebooks
- SKILL.md covers Step 1: Understand what the…, Step 2: Fetch the paper, Step 3: Plan the notebook and Step 4: Build the notebook, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Implement Paper is an agent skill from marimo-team/skills. Implement a research paper as an interactive marimo notebook together with the user. Start by understanding what the user wants to explore, fetch the paper via alphaxiv, then build a focused notebook.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/anywidget.md` and `references/fetching-papers.md`).
It sits in Research & Science, covering Jupyter notebooks. It works with marimo. The repository describes itself as: skills for coding agents related to marimo. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Jupyter notebooks
Example prompts
- “/implement-paper”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6454470. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Implement Paper loads about 1.1k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 571 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from marimo-team/skills at commit 6454470, republished under its Apache-2.0 licence (© marimo-team). 571 words, ~1,053 tokens.
Download SKILL.mdSave it as
.claude/skills/implement-paper/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- implement-paper
- description
- Implement a research paper as an interactive marimo notebook together with the user. Start by understanding what the user wants to explore, fetch the paper via alphaxiv, then build a focused notebook.
Implement Paper
Turn a research paper into an interactive marimo notebook. For general marimo notebook conventions (cell structure, PEP 723 metadata, output rendering, marimo check, variable naming, etc.), refer to the marimo-notebook skill.
Step 1: Understand what the user wants
Before fetching or reading anything, have a short conversation to scope the work. Ask the user:
- Which part of the paper interests you most? A paper may have multiple contributions — the user likely cares about one or two. Don't implement the whole thing.
- What's the goal? Are they trying to understand the method, reproduce a result, adapt it to their own data, or teach it to someone else? This changes the notebook's tone and depth.
- Do they want to use a specific dataset? If it's relevant, ask. Otherwise, suggest simulating data.
- Does this require PyTorch? Some papers need it, many don't. Ask if unclear — it's a heavy dependency.
- What's their background? The paper aims to fill a knowledge gap — gauge what the user already knows so the notebook can meet them where they are. Skip basics they're familiar with, explain prerequisites they're not.
Only move on once you have a clear picture of what to build.
Step 2: Fetch the paper
If the user gives you an Arxiv/AlphaXiv link, you will an efficient way to read the paper.
See references/fetching-papers.md for how to retrieve paper content via alphaxiv.org. This avoids reading raw PDFs and gives you structured markdown.
Step 3: Plan the notebook
After reading the paper, outline the notebook structure for the user before writing code.
Keep the notebook as small as possible. Sometimes the idea is best conveyed with just a single interactive widget — if you need a custom one, consider the anywidget skill. Other times you need a full training loop — if so, consider using the marimo-batch skill for heavy computation. The goal is the minimum amount of code needed to get the idea across.
A typical arc:
| Section | Purpose | Typical elements |
|---|---|---|
| Title & context | Orient the reader | mo.md() with paper title, authors, link |
| Background | Set up prerequisites | Markdown + equations |
| Method | Core algorithm step-by-step | Code + markdown interleaved |
| Experiments | Reproduce key results | Interactive widgets + plots |
| Conclusion | Summarize takeaways | mo.md() |
Not every notebook needs all sections. Share the outline with the user and adjust before writing code.
Show full SKILL.md (194 more words)Show less
Step 4: Build the notebook
Create the marimo notebook following the marimo-notebook skill conventions.
Key guidelines:
- Never assume the dataset. Use whatever the user specified in Step 1. If they didn't specify one, simulate data.
- Make it self-contained. A reader should understand the notebook without reading the full paper.
- Use KaTeX for equations. Render key equations with
mo.md(r"""$...$""")so the notebook mirrors the paper's notation. Keep notation consistent with the paper. - Add interactivity where it aids understanding. Sliders for hyperparameters, dropdowns for dataset variants, or toggles for ablations help readers build intuition.
- Show, don't just tell. Prefer a plot or table over a paragraph of explanation.
- Name variables to match the paper's notation where practical (e.g.,
alpha,X,W), and add comments mapping them to equation numbers.
Tips
- Don't reproduce the entire paper. Focus on what the user asked about in Step 1.
- Iterate visually. Build up figures incrementally (e.g., show data → show model fit → show residuals) rather than dumping everything into one plot.
- If the paper uses heavy notation, include a small "notation reference" cell with a markdown table mapping symbols to descriptions.
If the user wants a custom anywidget, refer to references/anywidget.md.
© marimo-team, 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
Files
SKILL.md and 2 other files (references) in skills/implement-paper of marimo-team/skills.
- SKILL.md
- references/anywidget.md
- references/fetching-papers.md
Open the folder on GitHubat commit 6454470
Compare with similar skills
Implement Paper 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 |
|---|---|---|---|---|---|---|
| Implement Paper this skillmarimo-team/skills | 174 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Wasm Compatibilityericmjl/llamabot | 182 | 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 | 140 | — | ~3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Marimo Pair
cosanlab/nltools
Work inside a running marimo notebook's kernel — execute code, create cells, and build a notebook as an artifact.
Marimo Notebook
cosanlab/nltools
Write a marimo notebook in a Python file in the right format.
Marimo Batch
koaning/gitcharts
An opintionated skill to prepare a marimo notebook to make it ready for a scheduled run.
Marimo Pair
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.
Phd Application Planner
SihengTao/phd-application-planner
Research and compare PhD or doctoral programs and fitting advisors, then build an evidence-aware marimo dashboard and optional Excel workbook.
More from marimo-team/skills
Auto Paper Demo
marimo-team/skills
Make a demo of a research paper in a marimo notebook fully automatically without extra user input.
Add Molab Badge
marimo-team/skills
Add "Open in molab" badge(s) linking to marimo notebooks. An agent skill from marimo-team/skills.
Streamlit To Marimo
marimo-team/skills
Convert a Streamlit app to a marimo notebook. An agent skill from marimo-team/skills.
Related
Works with
Categories
Questions about Implement Paper
What does Implement Paper do?
Implement a research paper as an interactive marimo notebook together with the user. Implement Paper is an agent skill from marimo-team/skills. Implement a research paper as an interactive marimo notebook together with the user.
When should I use Implement Paper?
Implement Paper fits situations like: tasks that involve Jupyter notebooks.
How do I install Implement Paper in Claude Code?
Run `npx skills add marimo-team/skills --skill implement-paper -a claude-code`. Or copy the skill folder (skills/implement-paper in marimo-team/skills) into .claude/skills/implement-paper in your project. Claude Code loads it when a task matches its description.
How do I install Implement Paper in Codex?
Run `npx skills add marimo-team/skills --skill implement-paper -a codex`. Or copy the skill folder (skills/implement-paper in marimo-team/skills) into .agents/skills/implement-paper in your project. Codex loads it when a task matches its description.
Can I use Implement Paper in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add marimo-team/skills --skill implement-paper -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implement-paper, .gemini/skills/implement-paper, .github/skills/implement-paper and .opencode/skills/implement-paper in your project.
What does Implement Paper need to run?
SKILL.md names no scripts, command-line tools or credentials: Implement Paper is instructions for the agent only.
Does Implement Paper access the network?
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.
Is Implement Paper safe to install?
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.
What licence does Implement Paper use?
Implement Paper 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.
How many tokens does Implement Paper use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Implement Paper?
Skills that share tags, products or a category with Implement Paper: Wasm Compatibility (ericmjl/llamabot, 182 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.
Who maintains Implement Paper?
marimo-team (a GitHub organization) maintains it in marimo-team/skills, which has 174 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 19, 2026.
Source: marimo-team/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.