whiteboard SKILL.md skillB
whiteboard from markphelps/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add markphelps/skills/whiteboard@git:20261001.004566bPins git:20261001.004566b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- markphelps/skills
- Path
development/skills/whiteboard/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.004566b, committed Oct 1, 2026
- First version recorded
- Sep 24, 2026
- Size
- 19,194 bytes
- Repository stars
- 6
- License
- MIT
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 Help the user pass the whiteboard defense on a codebase: if someone pulls them aside and asks how a system works, why it was built this way instead of another way, where it fails, or what happens when an actor misbehaves, they can answer confidently. Line-level recall is not the goal. A high-level, defensible mental model is. The skill has two halves that feed each other: 1. **Map.** Explore the repo and write a layered architecture map with receipts for every claim about _why_. 2. **Defend.** Quiz the user on the map, one question at a time, and record what they know, what they missed, and what the code failed to explain. ## Hard rules - **Never modify the working tree.** While mapping, refreshing, or defending, the only files this skill writes are under `docs/map/` (or the repo's existing docs location, see below) and `.map/`. Cleanup ideas go in the friction log, not in edits; changing code mid-map corrupts the thing being mapped. The one exception is `/whiteboard docs`, which writes to a separate branch in a `git worktree`, and changes source files only in a comments-only commit that passes the comment check (see `references/docs.md`). …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_46lnh3xdx4xx3f6e/fdc2212bd4f7fd3bb8c2a3e8e9e656e340538678d5ab1bac0251a3aa691b3abf.json
Then /plugin install whiteboard@markdownregistry-46lnh3xdx4xx3f6e in Claude Code. It installs git:20261001.004566b, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add markphelps/skills/whiteboard@sha256:fdc2212bd4f7fd3bThe line at the top of this page pins the label git:20261001.004566b, 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_46lnh3xdx4xx3f6e)
1 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 markphelps/skills/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 5 versions of this file, between Sep 24, 2026 and Oct 1, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.004566b latest | 2026-10-01 | 004566b | 19,194 B | B | view · diff |
| git:20260924.703753d | 2026-09-24 | 703753d | 17,563 B | B | view · diff |
| git:20260924.db9b2e4 | 2026-09-24 | db9b2e4 | 16,149 B | B | view · diff |
| git:20260924.c44a9c9 | 2026-09-24 | c44a9c9 | 13,937 B | B | view · diff |
| git:20260924.1414b05 | 2026-09-24 | 1414b05 | 13,277 B | B | 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
- fail: Frontmatter declares a description
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Size between 200 bytes and 200 KB (19194 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
markphelps/skills · 6 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_46lnh3xdx4xx3f6e GET https://markdownregistry.com/api/v1/resolve?ref=markphelps/skills/whiteboard GET https://markdownregistry.com/api/v1/blob/fdc2212bd4f7fd3bb8c2a3e8e9e656e340538678d5ab1bac0251a3aa691b3abf
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 markphelps/skills
Every file in markphelps/skills