agent-launcher-orchest…
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
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
$ npx -y skills add alirezarezvani/claude-skills --skill board-prep --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/board-prepContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: "board-prep" description: "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."
**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:**
1. **Where we are (honest)** — Current state of business, the real number, not the smoothed one 2. **What we learned** — What the data is telling us that we didn't know 90 days ago 3. **What we got wrong** — Name it directly. Don't make them ask. 4. **What we're doing about it** — Specific, dated, owned actions 5. **What we need from this room** — Concrete ask. Not "support" — specific introductions, decisions, resources.
**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:**
388 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools. The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 9 more coding agents.
Repo: alirezarezvani/claude-skills
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
Phase 3 of building a Claude Managed Agent — the bounded grade→iterate loop. Define a CMA outcome (a required markdown rubric graded by an isolated grader),…
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table +…
Phase 4 of building a Claude Managed Agent — make it run without you. Turn a graded agent into a recurring scheduled deployment (POSIX-cron), an event-driven…
Phase 2 of building a Claude Managed Agent — turn a validated build sheet into exact API payloads and a resumable BYOK curl launch script, then launch…
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2…