Napkin
github/awesome-copilot
Visual whiteboard collaboration for Copilot CLI. An agent skill from github/awesome-copilot.
Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute.
MITAuto-check passed
Install Whiteboard To Spec
$ npx skills add mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills whiteboard-to-spec --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/whiteboard-to-spec .claude/skills/whiteboard-to-spec && 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 "whiteboard-to-spec" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/whiteboard-to-spec into .claude/skills/whiteboard-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whiteboard-to-spec", 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/mohitagw15856/pm-claude-skills/tree/main/skills/whiteboard-to-specType 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 mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills whiteboard-to-spec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/whiteboard-to-spec .agents/skills/whiteboard-to-spec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "whiteboard-to-spec" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/whiteboard-to-spec into .agents/skills/whiteboard-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whiteboard-to-spec", 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 mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills whiteboard-to-spec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/whiteboard-to-spec .cursor/skills/whiteboard-to-spec && 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 "whiteboard-to-spec" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/whiteboard-to-spec into .cursor/skills/whiteboard-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whiteboard-to-spec", 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/mohitagw15856/pm-claude-skills.git --path skills/whiteboard-to-spec--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 mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills whiteboard-to-spec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/whiteboard-to-spec .gemini/skills/whiteboard-to-spec && 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 "whiteboard-to-spec" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/whiteboard-to-spec into .gemini/skills/whiteboard-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whiteboard-to-spec", 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 mohitagw15856/pm-claude-skills whiteboard-to-specInstalls 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 mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/whiteboard-to-spec .github/skills/whiteboard-to-spec && 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 "whiteboard-to-spec" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/whiteboard-to-spec into .github/skills/whiteboard-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whiteboard-to-spec", 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 mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills whiteboard-to-spec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/whiteboard-to-spec .opencode/skills/whiteboard-to-spec && 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 "whiteboard-to-spec" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/whiteboard-to-spec into .opencode/skills/whiteboard-to-spec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "whiteboard-to-spec", 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
whiteboard-to-spec- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 536 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute.
- Works in 5 steps: Transcribe first, interpret second. Pass… → Honour the visual grammar. Boxes =… → Redraw, don't describe. Flows and… → …
- Given whiteboard photos after a workshop
- SKILL.md covers What This Skill Produces, Required Inputs, Reading Method and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Whiteboard To Spec is an agent skill from mohitagw15856/pm-claude-skills. Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Use when given whiteboard photos after a workshop, sketch images of a flow or architecture, or asked to 'write up what we drew'. Produces a structured write-up — decisions, flows, open questions, owners — that preserves everything on the board and flags what was ambiguous. Requires image input.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Given whiteboard photos after a workshop
- Sketch images of a flow
- Asked to write up what we drew
Example prompts
- “write up what we drew”
- “/whiteboard-to-spec”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Transcribe first, interpret second. Pass one lists what is physically on the board, region by region (top-left, centre…), including…
- Honour the visual grammar. Boxes = entities/steps; arrows = flow or causality (note direction); crossed-out = considered and rejected…
- Redraw, don't describe. Flows and architectures become Mermaid diagrams or ordered steps, not paragraphs about arrows.
- Never invent legibility. Unreadable text becomes [illegible — looks like "…"] in the ambiguity ledger. A wrong guess presented confidently…
- Multiple photos: establish overlap first (same board, different angles vs. different boards) and merge without duplicating.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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 (its code samples are mermaid).
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
Whiteboard To Spec loads about 1.1k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 536 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 536 words, ~1,092 tokens.
Download SKILL.mdSave it as
.claude/skills/whiteboard-to-spec/SKILL.md (or your agent's skills folder).- name
- whiteboard-to-spec
- description
- Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Use when given whiteboard photos after a workshop, sketch images of a flow or architecture, or asked to 'write up what we drew'. Produces a structured write-up — decisions, flows, open questions, owners — that preserves everything on the board and flags what was ambiguous. Requires image input.
Whiteboard To Spec Skill
The whiteboard is where teams decide; the photo of it is where decisions go to die. This skill reads the photo like the person who was in the room — arrows, crossings-out, shorthand, spatial grouping — and produces the write-up that should have been made that afternoon.
What This Skill Produces
- A faithful transcription of everything legible on the board, organised by its spatial grouping
- The structured spec: decisions made, flows/diagrams redrawn as text or Mermaid, options considered (including crossed-out ones — rejections are decisions), open questions
- An ambiguity ledger: what couldn't be read or could mean two things, flagged instead of guessed
Required Inputs
- The image(s) — one or more photos of the board/wall/sketch. If none is attached, ask for it; never proceed on a verbal description alone.
- Context (ask if missing): what was the session about, who attended, what decision it served
Reading Method
- Transcribe first, interpret second. Pass one lists what is physically on the board, region by region (top-left, centre…), including arrows, boxes, colours, underlines, and crossings-out. Do not skip marginalia — the small note at the edge is often the real decision.
- Honour the visual grammar. Boxes = entities/steps; arrows = flow or causality (note direction); crossed-out = considered and rejected (keep it, labelled as rejected); circled/starred/underlined = emphasis; separate clusters = separate topics; a "?" = the room didn't agree.
- Redraw, don't describe. Flows and architectures become Mermaid diagrams or ordered steps, not paragraphs about arrows.
- Never invent legibility. Unreadable text becomes
[illegible — looks like "…"]in the ambiguity ledger. A wrong guess presented confidently poisons the whole spec. - Multiple photos: establish overlap first (same board, different angles vs. different boards) and merge without duplicating.
Output Format
Show full SKILL.md (257 more words)Show less
Board write-up: [session topic] — [date]
What the board says (transcription by region): [region] — [contents, verbatim where legible]
Decisions on the board:
| # | Decision | Evidence on the board | Confidence |
|---|---|---|---|
| [e.g. "circled, arrow from both options"] | high / read-between-lines |
Flows / structures (redrawn):
[the diagram the board was drawing]Considered and rejected: [crossed-out items, with what replaced them]
Open questions from the board: [every "?", disagreement marker, or dangling arrow]
Ambiguity ledger: [illegible or two-way-readable items — for the room to resolve]
Suggested next step: [the one action the board implies, e.g. "confirm decision #2 with the two owners named"]
Quality Checks
- Every legible element on the board appears somewhere in the write-up — nothing silently dropped
- Crossed-out content is preserved as "rejected", not omitted
- Diagrams are redrawn as Mermaid/steps, not prose descriptions of arrows
- Every uncertain reading is in the ambiguity ledger, not presented as fact
- Decisions carry their on-board evidence, so a sceptic can check the photo
Anti-Patterns
- Do not proceed without an image — this skill reads boards, it doesn't imagine them
- Do not "clean up" the room's thinking into what it should have decided — transcribe what it did decide
- Do not guess illegible words silently — a confident wrong guess is worse than a flagged gap
- Do not ignore spatial grouping — merging two separate clusters into one list destroys the meaning
- Do not drop the marginalia — initials, dates, and edge notes are often owners and deadlines
Example Trigger Phrases
- "Write up what we drew."
- "Turn these whiteboard photos into a spec."
- "Here's a photo of our sticky-note wall: make it a plan."
- "Turn this napkin sketch into a spec."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/whiteboard-to-spec of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Whiteboard To Spec 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 |
|---|---|---|---|---|---|---|
| Whiteboard To Spec this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Napkingithub/awesome-copilot | 40k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Photoscodewhale-hq/Codewhale | 41k | — | ~386 | Automated safety check: Pass | MIT | |
| Frame Flowchart Stickynexu-io/open-design | 100k | — | ~681 | Automated safety check: Pass | Apache-2.0 | |
| Meeting Notesoutline/outline | 41k | — | ~551 | Automated safety check: Pass | Custom licence | |
| Whiteboardedenfunf/reelmimic | 1.9k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Photos
codewhale-hq/Codewhale
Search a local macOS Photos library and export selected copies when the user asks to find or use their own photos.
Frame Flowchart Sticky
nexu-io/open-design
SVG curve connectors, sticky-note nodes, and cursor interaction with a whiteboard-brainstorm feel.
Meeting Notes
outline/outline
Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.
Whiteboard
edenfunf/reelmimic
Make hand-drawn whiteboard / doodle-explainer / sketch-note animation videos (MP4) with code — marker lines that draw themselves on, a cartoon hand holding a marker that follows the pen tip…
Meeting Notes And Actions
composio-community/awesome-codex-skills
Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Whiteboard To Spec
What does Whiteboard To Spec do?
Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute. Whiteboard To Spec is an agent skill from mohitagw15856/pm-claude-skills. Turn photos of a whiteboard, sticky-note wall, or napkin sketch into a structured spec the team can execute.
When should I use Whiteboard To Spec?
Whiteboard To Spec fits situations like: given whiteboard photos after a workshop; sketch images of a flow; asked to write up what we drew.
How do I install Whiteboard To Spec in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a claude-code`. Or copy the skill folder (skills/whiteboard-to-spec in mohitagw15856/pm-claude-skills) into .claude/skills/whiteboard-to-spec in your project. Claude Code loads it when a task matches its description.
How do I install Whiteboard To Spec in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a codex`. Or copy the skill folder (skills/whiteboard-to-spec in mohitagw15856/pm-claude-skills) into .agents/skills/whiteboard-to-spec in your project. Codex loads it when a task matches its description.
Can I use Whiteboard To Spec 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 mohitagw15856/pm-claude-skills --skill whiteboard-to-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/whiteboard-to-spec, .gemini/skills/whiteboard-to-spec, .github/skills/whiteboard-to-spec and .opencode/skills/whiteboard-to-spec in your project.
What does Whiteboard To Spec need to run?
SKILL.md names no scripts, command-line tools or credentials: Whiteboard To Spec is instructions for the agent only.
Does Whiteboard To Spec 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 Whiteboard To Spec 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 Whiteboard To Spec use?
Whiteboard To Spec is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Whiteboard To Spec use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Whiteboard To Spec?
Skills that share tags, products or a category with Whiteboard To Spec: Napkin (github/awesome-copilot, 40k stars), Photos (codewhale-hq/Codewhale, 41k stars), Frame Flowchart Sticky (nexu-io/open-design, 100k stars) and Meeting Notes (outline/outline, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Whiteboard To Spec?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.