whiteboard SKILL.md skillA
whiteboard from jimliu/open-artifact is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jimliu/open-artifact/whiteboard@git:20261118.d297a34Pins git:20261118.d297a34 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jimliu/open-artifact
- Path
artifact-types/whiteboard/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261118.d297a34, committed Nov 18, 2026
- First version recorded
- Nov 17, 2026
- Size
- 31,890 bytes
- Repository stars
- 54
- License
- Apache-2.0
Make and change a Whiteboard: a shared, infinite board where people and the agent lay out thinking together with sticky notes, shapes, sections, text, arrows, pen lines, pictures, tables, stickers, link cards and small working embeds. Its content is the board's own document store (small JSON documents under db/), written through ArtifactData under a host or `open-artifact write-db` locally, never as free-form files. Use when someone asks for a whiteboard, a brainstorm, a flowchart or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Whiteboard
A board is a folder, `<root>`. Its content is the documents under `<root>/db/`: `db/board/meta.json`
(title and stacking order) and one `db/elements/<id>.json` per element. A local page (started by
`open-artifact open`) draws the board, saves what people change back into the same documents, and shows what you
write as soon as you write it. `SKILL.md`, `reference/` and `scripts/` are the type's own files: leave them as they
are.
Standalone, a new board is a folder `designs/<slug>/` in the working directory unless the person names another
(`<slug>`: the title in lowercase words joined by `-`; a title not in Latin letters takes a short English rendering
of it). The first `write-db` that writes `board/meta` starts it.
`open-artifact` below stands for `node <this skill's folder>/scripts/cli.mjs` (Node 22 or later).
**With the Artifact tool** (an Open Artifact host runs this type for you): create a board with
`Artifact {action: "quickstart", intent: "other"}`, then `Artifact {action: "publish", type_url:
"open-artifact://type/whiteboard", title}`; its result gives the board's `url` (`open-artifact://artifact/<id>`). Read and
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_t3q7rpkg2xl4wdcj/78ef102634ca6f356a366ea29c883a3ea1b6cbb8cd347b901d67741d5f4cdc9a.json
Then /plugin install whiteboard@markdownregistry-t3q7rpkg2xl4wdcj in Claude Code. It installs git:20261118.d297a34, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add jimliu/open-artifact/whiteboard@sha256:78ef102634ca6f35The line at the top of this page pins the label git:20261118.d297a34, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_t3q7rpkg2xl4wdcj)
0 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in jimliu/open-artifact/whiteboard since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of whiteboard from somewhere else? Ask it: where did my whiteboard come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Nov 17, 2026 and Nov 18, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.d297a34 latest | 2026-11-18 | d297a34 | 31,890 B | A | view · diff |
| git:20261118.6975fec | 2026-11-18 | 6975fec | 31,701 B | A | view · diff |
| git:20261117.a6cd3e3 | 2026-11-17 | a6cd3e3 | 29,044 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/whiteboard/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (31890 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jimliu/open-artifact · 54 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t3q7rpkg2xl4wdcj GET https://markdownregistry.com/api/v1/resolve?ref=jimliu/open-artifact/whiteboard GET https://markdownregistry.com/api/v1/blob/78ef102634ca6f356a366ea29c883a3ea1b6cbb8cd347b901d67741d5f4cdc9a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from jimliu/open-artifact
Every file in jimliu/open-artifact