Token导航 LogoToken导航

Agent Skill · 待分类

board-prep(董事会准备)

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

board-prep 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 362。

总安装 19,053周安装 786GitHub Stars 13,189下载 6,225核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

/em:board-prep 为对抗型董事会会议做准备,预测所有严苛问题和所需冰冷数据。它构建承认弱点但不失掌控的叙事,涵盖财务、运营和战略层面的真实挑战呈现。适用于种子轮到成长阶段公司的董事会沟通强化训练,提升抗压和信息透明度。使用前需明确议程和关键痛点,避免美化或回避实质问题。

board-prep 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/board-prep

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/alirezarezvani/claude-skills --skill board-pre…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

board-prep 怎么安装?

在终端执行 npx skills add https://github.com/alirezarezvani/claude-skills --skill board-prep。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

board-prep 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

board-prep 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

board-prep 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

board-prep 用的人多吗?

公开数据是累计安装 19,053 次,近一周安装 786 次,下载 6,225 次,GitHub 13,189 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

board-prep 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 13,189 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
board-prep

董事会准备 · 本页

19,05313,189权限未标注未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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.

平台分布

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