Token导航 LogoToken导航TokenDH.com
待分类权限需确认github未标认证来源可访问许可证需确认审计通过

board-prep董事会准备

Agent Skill

board-prep 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

19,053

周安装

786

GitHub Stars

13,189

下载量

6,225
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:board-prep(董事会准备)
来源仓库:https://github.com/alirezarezvani/claude-skills
仓库路径:skills/board-prep
安装命令:
npx skills add https://github.com/alirezarezvani/claude-skills --skill board-prep
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/alirezarezvani/claude-skills --skill board-prep

简介

/em:board-prep 为对抗型董事会会议做准备,预测所有严苛问题和所需冰冷数据。

  • 它构建承认弱点但不失掌控的叙事,涵盖财务、运营和战略层面的真实挑战呈现。
  • 适用于种子轮到成长阶段公司的董事会沟通强化训练,提升抗压和信息透明度。
  • 使用前需明确议程和关键痛点,避免美化或回避实质问题。
  • board-prep 属于待分类类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

/em:board-prep — Board Meeting Preparation

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.


The Reality of Board Meetings

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.


The Preparation Framework

Phase 1: Numbers Cold

Before the meeting, every number in your deck should live in your head, not just the slide.

The numbers you must know without looking:

  • Current MRR / ARR and month-over-month growth rate
  • Burn rate (monthly) and runway (months at current burn)
  • Headcount by department
  • CAC and LTV by channel / segment
  • Net Revenue Retention
  • Pipeline: value, conversion rate, average sales cycle
  • Churn: rate, top reasons, top churned accounts
  • Gross margin (product), net margin (company)
  • Key hiring positions open and time-to-fill

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.

Phase 2: Anticipate the Hard Questions

For every item on the agenda, generate the adversarial version of the question.

Standard adversarial questions by topic:

*Revenue performance:*

  • "You missed revenue by 20% this quarter. What specifically failed?"
  • "Is this a pipeline problem, a conversion problem, or a capacity problem?"
  • "If you missed because of one big deal, how dependent is your model on individual deals?"
  • "When do you project recovery and what are the leading indicators you're right?"

*Runway / burn:*

  • "At current burn you have N months. What's your plan if the next round takes 9 months?"
  • "What would you cut first if you had to extend runway by 6 months today?"
  • "Is there a scenario where you don't raise another round?"

*Product / roadmap:*

  • "You shipped X. What did customers actually do with it?"
  • "What did you kill this quarter and why?"
  • "Where are you behind on roadmap? What's slipping?"

*Team:*

  • "Who's at risk of leaving? How would that affect execution?"
  • "You've had 3 VP-level hires not work out. What pattern do you see?"
  • "Is the team the right team for this stage?"

*Competition:*

  • "Competitor Y just raised $50M. How does that change your position?"
  • "If they copy your best feature in 90 days, what's your moat?"

Phase 3: Build the Narrative

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."

Phase 4: Adversarial Preparation

Do a mock board meeting. Have someone play the hardest director you have.

The simulation:

  • Present your deck as you would
  • The mock director asks every uncomfortable question
  • You answer without referring to the deck
  • After: note every question that made you pause or feel defensive

The questions that made you defensive = the questions you need to prepare for.

Phase 5: Director-by-Director Prep

Not all board members want the same thing from a meeting.

For each director, know:

  • Their primary concern right now (usually tied to their investment thesis)
  • The metric they watch most closely
  • What would make them lose confidence in you
  • What they've said in the last meeting that you should address

Common director types:

  • The operator — wants to know what's breaking and who owns fixing it
  • The financial investor — focused on path to profitability or next raise
  • The strategic investor — worried about competitive position and moat
  • The independent — watching governance, team dynamics, and your judgment

Pre-Meeting Checklist

48 hours before:

  • All numbers verified against source systems (not last week's export)
  • Deck reviewed for internal consistency
  • Pre-read sent to board (deck + 1-page brief on key topics)
  • One-on-ones done with any director likely to have concerns
  • 3 hardest questions you expect — rehearsed out loud

Day of meeting:

  • Agenda with time allocations distributed
  • Know the ask for each agenda item (decision needed, input wanted, FYI)
  • Materials to leave behind prepared
  • Follow-up action template ready

During the Meeting

What the board is watching:

  • Do you own the bad news or deflect it?
  • Are you defending a narrative or sharing reality?
  • Do you know your numbers or do you look things up?
  • When challenged, do you get defensive or engage?
  • Do you know what you don't know?

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."


After the Meeting

Within 24 hours:

  • Send action items with owners and dates
  • Send any data you promised but didn't have
  • Note the questions that came up you weren't ready for
  • Schedule follow-up with any director who seemed unsatisfied

The next board prep starts now.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

39.2%
按下载量换算2,440

Claude

29.72%
按下载量换算1,850

Cursor

19.26%
按下载量换算1,199

Gemini CLI

9.53%
按下载量换算593

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills