Board meeting preparation for the adversarial scenario, not the friendly one. Forces numbers-cold mastery, anticipates hard questions, builds a narrative that acknowledges weakness without losing the room. Use when preparing for a board meeting, an investor update, fundraising presentation, or any high-stakes adversarial review where every number must live in your head not just on a slide.
cd ~/.claude/skills
git clone https://github.com/alirezarezvani/claude-skills.git claude-skills mkdir -p ~/.claude/skills/board-prep
curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-skills/HEAD/.gemini/skills/board-prep/SKILL.md \
-o ~/.claude/skills/board-prep/SKILL.md Command: /em:board-prep <agenda>
Prepare for the adversarial version of your board, not the friendly one. Every hard question they’ll ask. Every number you need cold. The narrative that acknowledges weakness without losing the room.
Your board members have seen 50+ companies. They’ve watched founders flinch at their own numbers, spin bad news as “learning opportunities,” and present sanitized decks that hide what’s actually happening.
They know when you’re not being straight with them. The question isn’t whether they’ll ask the hard questions — it’s whether you’re ready for them.
The best board meetings aren’t the ones where everything looks good. They’re the ones where the CEO demonstrates they see reality clearly, have a plan, and can execute under pressure.
Before the meeting, every number in your deck should live in your head, not just the slide.
The numbers you must know without looking:
Stress test yourself: Can you answer “what’s your burn?” without hesitation? “What’s your churn rate by segment?” If you pause, you don’t know it.
For every item on the agenda, generate the adversarial version of the question.
Standard adversarial questions by topic:
Revenue performance:
Runway / burn:
Product / roadmap:
Team:
Competition:
The board meeting isn’t a status update. It’s a leadership demonstration.
The structure that works:
The rule on bad news: Never let the board be surprised. If a quarter went badly, they should know before the deck. A 5-sentence email 3 days before: “Revenue came in at $X vs $Y target. Here’s what happened, here’s what I’m doing, here’s what I need from you.”
Do a mock board meeting. Have someone play the hardest director you have.
The simulation:
The questions that made you defensive = the questions you need to prepare for.
Not all board members want the same thing from a meeting.
For each director, know:
Common director types:
48 hours before:
Day of meeting:
What the board is watching:
The single best thing you can do: Name the hard thing before they do. “I want to address the revenue miss directly. Here’s what happened, here’s what I should have caught earlier, here’s what changes.”
Within 24 hours:
The next board prep starts now.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a C
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack.