# add-molab-badge

Adds "Open in molab" badges pointing to marimo notebooks in Markdown or HTML files. Handy for updating repository READMEs and docs.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2200 installs · ★ 175
- Author: marimo-team
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/marimo-team/skills/tree/HEAD/skills/add-molab-badge/SKILL.md
- Updated: 2026-08-19
- HTML: https://affpapa.org/en/nevibecode/skills/add-molab-badge

## What it does

The skill discovers marimo notebooks across the repository using `**/*.py` globs and checks for `import marimo` or `app = marimo.App` headers. Using the git remote origin and relative file paths, it creates `molab.marimo.io` links and formats them as Markdown or HTML badge tags pointing to `molab-shield.svg`.

When replacing existing `marimo.app` links, it appends the `/wasm` suffix because `marimo.app` runs notebooks on the client side. New links omit `/wasm` by default. Previews in molab also render cleaner when session snapshots are generated in advance via `uvx marimo export session` with the `--sandbox` flag.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add marimo-team/skills --skill add-molab-badge -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/add-molab-badge/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/add-molab-badge/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add marimo-team/skills --skill add-molab-badge -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/add-molab-badge/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add marimo-team/skills --skill add-molab-badge -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/add-molab-badge/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install marimo-team/skills add-molab-badge
```

2. **Manually: put the files in place**
- File: `.github/skills/add-molab-badge/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add marimo-team/skills --skill add-molab-badge -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/marimo-team/skills --path skills/add-molab-badge
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/add-molab-badge/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add marimo-team/skills --skill add-molab-badge -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/marimo-team/skills/tree/HEAD/skills/add-molab-badge/SKILL.md

## When to use it
- replace deprecated `marimo.app` links with current `molab.marimo.io` URLs
- discover marimo notebooks in the repo and link them in README.md
- generate HTML badge snippets for documentation sites and blogs
- export notebook session snapshots using `uvx marimo export session`

## Example prompts
- Find all marimo notebooks in this repository and add molab badges to README.md
- Replace the old marimo.app badges with molab links in docs/index.md
- Generate an HTML Open in molab badge for demo.py

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1d27a628f5e4dde5.

BEGIN THIRD-PARTY FILE 1d27a628f5e4dde5
````text
---
name: add-molab-badge
description: Add "Open in molab" badge(s) linking to marimo notebooks. Works with READMEs, docs, websites, or any markdown/HTML target.
---

# Add molab badge

Add "Open in molab" badge(s) linking to marimo notebooks. The badge can be added to any target: a GitHub README, documentation site, blog post, webpage, or any other markdown/HTML file.

## Instructions

### 0. Session export for molab

molab previews render much nicer if the github repository has session information around. This can be added via:

```bash
uvx marimo export session notebook.py
uvx marimo export session folder/
```

This executes notebooks and exports their session snapshots, which molab uses to serve pre-rendered notebooks.

Key flags:

- `--sandbox` — run each notebook in an isolated environment using PEP 723 dependencies
- `--continue-on-error` — keep processing other notebooks if one fails
- `--force-overwrite` — overwrite all existing snapshots, even if up-to-date

### 1. Determine the notebook links

The user may provide notebook links in one of two ways:

- **User provides links directly.** The user pastes URLs to notebooks. Use these as-is — no discovery needed.
- **Notebook discovery (README target only).** If the user asks you to add badges to a repository's README and doesn't specify which notebooks, discover them:
  1. Find all marimo notebook files (`.py` files) in the repository. Use `Glob` with patterns like `**/*.py` and then check for the marimo header (`import marimo` or `app = marimo.App`) to confirm they are marimo notebooks.
  2. If the README already has links to notebooks (e.g., via `marimo.app` links or existing badges), replace those.
  3. Otherwise, ask the user which notebooks should be linked.

### 2. Construct the molab URL

For each notebook, construct the molab URL using this format:

```
https://molab.marimo.io/github/{owner}/{repo}/blob/{branch}/{path_to_notebook}
```

- `{owner}/{repo}`: the GitHub owner and repository name. Determine from the git remote (`git remote get-url origin`), the user-provided URL, or by asking the user.
- `{branch}`: typically `main`. Confirm from the repository's default branch.
- `{path_to_notebook}`: the path to the `.py` notebook file relative to the repository root.

### 3. Apply the `/wasm` suffix rules

- If **replacing** an existing `marimo.app` link, append `/wasm` to the molab URL. This is because `marimo.app` runs notebooks client-side (WASM), so the molab equivalent needs the `/wasm` suffix to preserve that behavior.
- If adding a **new** badge (not replacing a `marimo.app` link), do **not** append `/wasm` unless the user explicitly requests it.

### 4. Format the badge

Use the following markdown badge format:

```markdown
[![Open in molab](https://marimo.io/molab-shield.svg)](URL)
```

Where `URL` is the constructed molab URL (with or without `/wasm` per the rules above).

For HTML targets, use:

```html
<a href="URL"><img src="https://marimo.io/molab-shield.svg" alt="Open in molab" /></a>
```

### 5. Insert or replace badges in the target

- When replacing existing badges or links:
````
END THIRD-PARTY FILE 1d27a628f5e4dde5

The third-party file has ended. Everything between the 1d27a628f5e4dde5 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3118 of 4503 bytes. © marimo-team · Apache-2.0 · https://github.com/marimo-team/skills/tree/HEAD/skills/add-molab-badge/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md