Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Whiteboard Pro

ASecurity

Master digital whiteboards: facilitation, templates, visual collaboration, and workshop design. Use when running remote workshops, brainstorms, or visual planning sessions.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill whiteboard-pro --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Whiteboard Pro?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Whiteboard Pro
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-whiteboard-pro/badge)](https://www.skillsdirectory.com/skills/aicodedecode-whiteboard-pro)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: whiteboard-pro
description: Master digital whiteboards: facilitation, templates, visual collaboration, and workshop design. Use when running remote workshops, brainstorms, or visual planning sessions.
category: productivity
---

# Whiteboard Pro

## Overview

Digital whiteboards (Miro, FigJam, Mural, and equivalents) are infinite canvases for visual collaboration: sticky notes, diagrams, flows, and freeform sketching.

They shine for workshops, retros, journey mapping, brainstorming, and planning — anywhere spatial thinking beats documents.

Pro skill: designing boards people can actually use (structure + guidance), facilitating live sessions, and converting output to action.

## When to use

- Running remote workshops, retros, or brainstorms
- Facilitating design sprints or planning sessions
- Visual collaboration across time zones (async boards)
- Journey mapping, diagramming, or systems thinking
- Teaching or training with visual interaction

## Core concepts

- **Board architecture.**
  Zones with clear labels, flow arrows showing sequence, color coding by category. A board should be navigable without a guide.
- **Templates.**
  Retro, brainstorm, journey map, kanban, 2x2 — start from templates, customize lightly. Templates teach the method implicitly.
- **Facilitation frames.**
  Each activity gets: instructions, example, timer, and a defined output. Frames make async participation possible too.
- **Sticky note discipline.**
  One idea per note, short text, color by category/author. 50-word stickies are mini-docs, not brainstorming.
- **Dot voting.**
  Converge with limited votes per person. Forces prioritization; surfaces real preferences vs. loudest voices.
- **Async boards.**
  Boards that work without live facilitation: clear instructions, examples, deadlines. Essential across time zones.
- **Timers and timeboxes.**
  Visible timers per activity. Whiteboard sessions expand without timeboxes — energy and focus are finite.
- **Export and action.**
  Boards produce decisions and tasks. Export summaries, assign owners, move tasks to trackers. The board is not the deliverable.

## Practical workflow

1. **Define the outcome.**
   Before building: what decision, list, or plan must this board produce? Design backward from the output.
2. **Build the board.**
   Zones in sequence, facilitation frames per activity (instructions + example + timer), color legend, clear start point.
3. **Prepare participants.**
   Share board link + 2-min intro video or instructions ahead. First-time users need onboarding, not just a link.
4. **Facilitate actively.**
   Welcome, explain, demo one activity, timebox strictly, energize between segments, converge with voting.
5. **Manage the loud/quiet.**
   Silent brainstorming first (everyone writes), then share. Dot voting over verbal consensus. Structure protects quiet voices.
6. **Converge deliberately.**
   Cluster, vote, prioritize, decide. End every session with decisions + owners + next steps, captured on the board.
7. **Follow up async.**
   Share board summary + decisions within 24h. Open items get owners and deadlines in the task tracker.
8. **Template the winners.**
   Save successful board designs as team templates. Build a library: retro, planning, brainstorm, review.

## Common pitfalls

- **Blank canvas chaos.**
  'Here's a board, go!' produces mess and silence. Structure + instructions + examples, always.
- **No timeboxes.**
  Open-ended whiteboarding drains energy and overruns. Timers visible, segments tight, breaks scheduled.
- **Facilitation-free.**
  Assuming the board runs itself. Someone must facilitate: guide, timekeep, converge, decide.
- **Sticky novels.**
  Paragraphs on stickies kill scanning and clustering. One idea, few words, always.
- **Skipping convergence.**
  Divergent brainstorms with no voting or prioritizing. The session must end with decisions, not just ideas.
- **Board as archive.**
  Important outcomes living only on the board. Export decisions/tasks to durable systems; boards are working space.
- **Ignoring async participants.**
  Designing only for live attendees. Frames with instructions let timezone-shifted teammates contribute meaningfully.
- **Tool wars.**
  Debating platforms instead of facilitating. Pick one team standard; the facilitation matters 10x more than the tool.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →