Wasm Compatibility
ericmjl/llamabot
Check if a marimo notebook is compatible with WebAssembly (WASM) and report any issues.
Make a demo of a research paper in a marimo notebook fully automatically without extra user input.
$ npx skills add marimo-team/skills --skill auto-paper-demo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install marimo-team/skills auto-paper-demo --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/auto-paper-demo .claude/skills/auto-paper-demo && 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 "auto-paper-demo" agent skill from https://github.com/marimo-team/skills/tree/main/skills/auto-paper-demo into .claude/skills/auto-paper-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-paper-demo", 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/auto-paper-demoType 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 auto-paper-demo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install marimo-team/skills auto-paper-demo --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/auto-paper-demo .agents/skills/auto-paper-demo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "auto-paper-demo" agent skill from https://github.com/marimo-team/skills/tree/main/skills/auto-paper-demo into .agents/skills/auto-paper-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-paper-demo", 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 auto-paper-demo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install marimo-team/skills auto-paper-demo --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/auto-paper-demo .cursor/skills/auto-paper-demo && 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 "auto-paper-demo" agent skill from https://github.com/marimo-team/skills/tree/main/skills/auto-paper-demo into .cursor/skills/auto-paper-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-paper-demo", 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/auto-paper-demo--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 auto-paper-demo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install marimo-team/skills auto-paper-demo --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/auto-paper-demo .gemini/skills/auto-paper-demo && 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 "auto-paper-demo" agent skill from https://github.com/marimo-team/skills/tree/main/skills/auto-paper-demo into .gemini/skills/auto-paper-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-paper-demo", 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 auto-paper-demoInstalls 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 auto-paper-demo -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/auto-paper-demo .github/skills/auto-paper-demo && 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 "auto-paper-demo" agent skill from https://github.com/marimo-team/skills/tree/main/skills/auto-paper-demo into .github/skills/auto-paper-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-paper-demo", 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 auto-paper-demo -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 auto-paper-demo --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/auto-paper-demo .opencode/skills/auto-paper-demo && 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 "auto-paper-demo" agent skill from https://github.com/marimo-team/skills/tree/main/skills/auto-paper-demo into .opencode/skills/auto-paper-demo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-paper-demo", 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.
auto-paper-demoMake a demo of a research paper in a marimo notebook fully automatically without extra user input.
Auto Paper Demo is an agent skill from marimo-team/skills. Make a demo of a research paper in a marimo notebook fully automatically without extra user input.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/ANYWIDGET.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.
Read from SKILL.md and the folder at commit 6454470. 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.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
arxiv.orgalphaxiv.orgFrom 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.
Auto Paper Demo loads about 1k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 29 tokens; SKILL.md has 606 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 marimo-team/skills at commit 6454470, republished under its Apache-2.0 licence (© marimo-team). 606 words, ~1,012 tokens.
.claude/skills/auto-paper-demo/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.You need to come up with a compelling story to tell from a paper. Do not ask the user for feedback/input. You need to apply thinking and come up with the best story yourself.
Use alphaxiv.org to get structured, LLM-friendly paper content. This is faster and more reliable than trying to read a raw PDF.
Parse the paper ID from whatever the user provides:
| Input | Paper ID |
|---|---|
https://arxiv.org/abs/2401.12345 | 2401.12345 |
https://arxiv.org/pdf/2401.12345 | 2401.12345 |
https://alphaxiv.org/overview/2401.12345 | 2401.12345 |
2401.12345v2 | 2401.12345v2 |
2401.12345 | 2401.12345 |
curl -s "https://alphaxiv.org/overview/{PAPER_ID}.md"Returns a structured, detailed analysis of the paper as plain markdown. One call, no JSON parsing.
If the overview doesn't contain the specific detail you need (e.g., a particular equation, table, or proof):
curl -s "https://alphaxiv.org/abs/{PAPER_ID}.md"Returns the full extracted text of the paper as markdown.
https://arxiv.org/pdf/{PAPER_ID}.A good implementation tells a story, that's the most important thing. The story should be simple, but it should not be missing.
Papers typically have more than one concept in them. So that means you need to pick a story! It isn't the goal to fully implement the paper or to rerun a giant benchmark. The goal is to take a lesson/idea and to explain that very clearly in a notebook that can simply run on a CPU. That way, a user can easily run learn something from it. When you look at the notebook, what is the main concept or idea that you think is worth exploring? What is the concept that tells a story?
Pick the idea that is easiest to explain with a minimum code example. For a minimum code example to really work, it tends to help to have one, maybe two charts to look at. Maybe there's a dropdown that lets you try out different settings. Possibly even a slider. But the one thing we would want to do is prevent that the user needs to do a lot of scrolling.
It will be typical that you'll want to compare two approaches. But take a moment to think about the example, because that matters most to the story. Most of the time you don't want to use a toy example. They're not informative and they are overdone. It may be better to generate a creative example that shows where one approach can really shine. We don't want to cherry pick, but we also don't want to do examples that have been overdone either.
I cannot stress enough how important it is to actually think about the story and the example before you write any code whatsoever. You should really ultra think this. Give the user some interaction but really try to prevent scrolling. A good example tells a story, it doesn't just state some facts.
Feel free to think about this decision, but once you've got it clear what idea is best to showcase, immediately proceed to build the marimo notebook.
Use the marimo-notebook skill for this, and possibly the anywidget skill, but only if a custom widget makes for a better story. If you strongly feel that it makes sense to use a custom anywidget, refer to references/ANYWIDGET.md.
When you are ready, make sure that you hide all the code and that you move the cells with inputs/outputs to the top of the file.
Example:
@app.cell
def _(hide_code=True):
import marimo as mo
return mo© 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
SKILL.md and 1 other file (references) in skills/auto-paper-demo of marimo-team/skills.
Open the folder on GitHubat commit 6454470
Auto Paper Demo 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 |
|---|---|---|---|---|---|---|
| Auto Paper Demo this skillmarimo-team/skills | 175 | — | ~1k | 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.
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.
marimo-team/skills
Add "Open in molab" badge(s) linking to marimo notebooks. An agent skill from marimo-team/skills.
marimo-team/skills
Implement a research paper as an interactive marimo notebook together with the user.
marimo-team/skills
Convert a Streamlit app to a marimo notebook. An agent skill from marimo-team/skills.
Works with
Categories
Make a demo of a research paper in a marimo notebook fully automatically without extra user input. Auto Paper Demo is an agent skill from marimo-team/skills. Make a demo of a research paper in a marimo notebook fully automatically without extra user input.
Auto Paper Demo fits situations like: tasks that involve Jupyter notebooks.
Run `npx skills add marimo-team/skills --skill auto-paper-demo -a claude-code`. Or copy the skill folder (skills/auto-paper-demo in marimo-team/skills) into .claude/skills/auto-paper-demo in your project. Claude Code loads it when a task matches its description.
Run `npx skills add marimo-team/skills --skill auto-paper-demo -a codex`. Or copy the skill folder (skills/auto-paper-demo in marimo-team/skills) into .agents/skills/auto-paper-demo 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 marimo-team/skills --skill auto-paper-demo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-paper-demo, .gemini/skills/auto-paper-demo, .github/skills/auto-paper-demo and .opencode/skills/auto-paper-demo in your project.
Going by SKILL.md and its folder, Auto Paper Demo needs the command-line tools its instructions call (curl).
SKILL.md names 2 domains. In commands or code: arxiv.org and alphaxiv.org; the agent is likely to contact these when it follows the instructions. 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.
Auto Paper Demo 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 1k tokens (SKILL.md is roughly 4k 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 958 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Auto Paper Demo: 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.
marimo-team (a GitHub organization) maintains it in marimo-team/skills, which has 175 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.