Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计通过

board-deck-builder甲板建造者

Agent Skill

board-deck-builder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,483

周安装

60

GitHub Stars

103

下载量

466
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill board-deck-builder

简介

构建具有叙事逻辑的董事会汇报材料,强调数据背后的业务洞察。

  • 适用于季度复盘、融资路演与投资方沟通场景。
  • 提供指标选取、坏消息传达与方差解释的标准话术框架。
  • 需提前与利益相关者对齐预期,确保信息传递清晰且无误导。
  • board-deck-builder 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Board Deck Builder

Build board decks that tell a story, not just show data. Every section has an owner, a narrative, and a "so what." Boards see 10+ decks per quarter -- yours needs a through-line.

Keywords

board deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board narrative, QBR, quarterly business review, board report, metrics dashboard, bad news delivery, variance explanation


Deck Types and Structure

Deck Type Selection

TypeWhenSlide CountSent in AdvanceKey Section
Quarterly Board DeckStandard board meeting20-30 slides48 hours aheadFull deck below
Monthly UpdateEarly-stage boards8-12 slides24 hours aheadMetrics + risks
Fundraising DeckActive fundraise12-15 slidesDuring meetingVision + traction
Emergency/Ad-hocCrisis or major decision5-8 slidesDependsSituation + options

Standard Board Deck (Section by Section)

Section 1: Executive Summary (CEO)

Three sentences. No more. No less.

SentencePurposeExample
1State of the business"We closed Q3 at $2.4M ARR, up 22% QoQ"
2Biggest development this period"Signed our largest enterprise contract ($180K ACV)"
3Forward-looking priority"Q4 priority: close Series A and hit $2.8M ARR"

Anti-pattern: "We had a good quarter with lots of progress across all areas." Why it fails: Says nothing. Board learns nothing. Time wasted.

Section 2: Key Metrics Dashboard (COO)

6-8 metrics maximum. Every metric needs a target and a status.

MetricThis PeriodLast PeriodTargetStatusTrend
ARR$2.4M$1.97M$2.3M[G]Up
MoM Growth8.1%7.2%7.5%[G]Up
Burn Multiple1.8x2.1x< 2x[G]Improving
NRR112%108%> 110%[G]Up
CAC Payback11 mo14 mo< 12 mo[G]Improving
Headcount242125[Y]Below plan

Rule: Only show metrics the board actually tracks. Ask what they care about. Remove anything they have said they do not care about.

Section 3: Financial Update (CFO)

ComponentIncludeFormat
P&L SummaryRevenue, COGS, Gross Margin, OpEx, Net BurnTable with variance column
Cash PositionCurrent balance + runway in monthsSingle number, bold
Burn Multiple Trend3-quarter trendLine chart
Variance to PlanEach line item vs. budgetTable with one-sentence explanations
Forecast UpdateNext quarter projectionsConservative, base, upside

Rule: Every variance needs a one-sentence explanation. "Revenue was below target" with no explanation is unacceptable.

Section 4: Revenue and Pipeline (CRO)

ComponentIncludeFormat
ARR WaterfallOpening -> New -> Expansion -> Contraction -> Churn -> ClosingWaterfall chart
NRR and Logo ChurnCurrent + 4-quarter trendTable + trend line
Pipeline by StageDollar amounts, not just countsFunnel visualization
ForecastNext quarter with confidence level"High confidence $2.6M, upside to $2.9M"
Top 3 DealsName, amount, close date, riskTable

Rule: Forecast MUST include a confidence level. "We expect $2.8M" is weak.

Section 5: Product Update (CPO)

ComponentIncludeFormat
Shipped This Quarter3-5 items with user impactBullet list
Shipping Next Quarter3-5 items with target datesBullet list
PMF SignalsNPS trend, DAU/MAU, feature adoptionMetrics table
Key LearningOne insight from customer researchNarrative paragraph

Rule: No feature lists. Only features with evidence of user impact.

Section 6: Growth and Marketing (CMO)

ComponentInclude
CAC by ChannelTable with efficiency trend
Pipeline Contribution$ by channel
What's WorkingSpecific channels/campaigns with data
What's Being CutUnderperforming channels
What's Being TestedNew experiments with hypothesis

Section 7: Engineering and Technical (CTO)

ComponentInclude
Delivery Velocity4-quarter trend
Tech Debt RatioCurrent + plan to address
InfrastructureUptime, incidents, cost trend
Security PostureOne line unless there is a material issue

Rule: Keep this short unless there is a material issue. Boards do not need sprint details.

Section 8: Team and People (CHRO)

ComponentInclude
HeadcountActual vs. plan
HiringOffers out, pipeline, time-to-fill trend
AttritionRegrettable vs. non-regrettable
EngagementLatest survey score and trend
NotableKey hires, key departures, key open roles

Section 9: Risk and Security (CISO)

ComponentInclude
Security PostureStatus of critical controls
ComplianceCertifications in progress, deadlines
IncidentsThis quarter (if any): impact, resolution, prevention
Top 3 RisksRisk description + mitigation status

Section 10: Strategic Outlook (CEO)

ComponentInclude
Next Quarter Priorities3-5 items, ranked by importance
Board Decisions NeededSpecific votes or approvals
AsksSpecific, actionable requests

Rule: The "asks" section is the most important. "We'd like 3 warm introductions to CFOs at Series B companies" beats "any help would be appreciated."

Section 11: Appendix

Include but do not present unless asked:

  • Detailed financial model
  • Full pipeline data
  • Cohort retention charts
  • Customer case studies
  • Detailed headcount breakdown

Narrative Framework

The 4-Act Structure

Every board deck should follow this through-line:

Act 1: WHERE WE SAID WE'D BE
  Last quarter's targets and commitments

Act 2: WHERE WE ACTUALLY ARE
  Honest assessment -- good and bad

Act 3: WHY THE GAP EXISTS
  One cause per variance. Not excuses -- explanations.

Act 4: WHAT WE'RE DOING ABOUT IT
  Specific, dated, owned actions

This works for good news AND bad news. It is credible because it acknowledges reality.

Opening Frame

The board should know the key message by slide 3, not slide 30.

Good OpeningBad Opening
"We beat ARR target by 8% and NRR hit 112%""Let me walk you through our quarter..."
"We missed revenue by $300K. Here's why and the fix.""First, some context about market conditions..."
"We need a board vote on the acquisition opportunity""Before we get to the main topic, some updates..."

Delivering Bad News

The SOUF Framework

StepWhatExample
StateState it plainly"We missed Q3 ARR target by $300K (12% gap)"
OwnOwn the cause"Primary driver: longer enterprise sales cycle than modeled"
UnderstandShow you understand it"Analyzed 8 stalled deals; pattern is procurement delays"
FixPresent the fix"Three changes: [specific, dated], revised Q4 target: $2.6M"

Bad News Anti-Patterns

Anti-PatternWhy It FailsBetter Approach
Leading with good news to softenBoards notice and distrust framingLead with the most important thing
"Market conditions" as causeThat is context, not a causeName specific, controllable causes
Fix without dataBoard does not trust unfounded fixesShow analysis behind the fix
Revised forecast without assumptionsLooks like guessingShow bottom-up build

Common Board Deck Mistakes

MistakeFix
Too many slides (> 25)Cut ruthlessly. If you can not explain it, the slide is wrong.
Metrics without targetsEvery metric needs a target and a status indicator
No narrativeData without story forces boards to draw conclusions
Burying bad newsLead with it, own it, fix it
Vague asksSpecific, actionable, person-assigned asks only
No variance explanationEvery gap from target needs a one-sentence cause
Stale appendixAppendix is only useful if current
Designed for reader, not roomDecks are presented -- they must work spoken aloud
Inconsistent formattingUse one template, one color scheme, one font
Too much text per slideMax 6 lines per slide. Use speaker notes for detail.

Cadence Notes

TypeTimingLengthAdvance Send
Quarterly (standard)48 hours before meeting20-30 slides48 hours
Monthly (early-stage)24 hours before meeting8-12 slides24 hours
FundraisingIn the meeting12-15 slidesSometimes not shared

Deck Assembly Workflow

T-14 days: CEO sets agenda, identifies key messages
T-10 days: Section owners begin drafting their sections
T-7 days:  First drafts due. CEO reviews for narrative alignment.
T-5 days:  Second drafts. CFO validates all numbers.
T-3 days:  Final deck assembly. Narrative check.
T-2 days:  Send to board. Include cover note with 3 key takeaways.
T-0:       Meeting. CEO presents. Section owners available for questions.

Red Flags

  • Deck assembled night before the meeting -- no time for review or narrative alignment
  • Numbers in deck do not match financial model -- credibility destroyer
  • No asks section -- wasting board meeting time
  • Same deck format for 4+ quarters with no iteration -- not responsive to feedback
  • Board members surprised by information -- they should never learn bad news in the meeting
  • More than 30 slides -- attention lost after slide 20
  • No follow-up on previous meeting's action items -- accountability gap

Integration with C-Suite

Each section is owned by a specific C-suite role:

SectionOwnerReference Skill
Executive SummaryCEOceo-advisor
Metrics DashboardCOOcoo-advisor
Financial UpdateCFOcfo-advisor
Revenue/PipelineCROcro-advisor
Product UpdateCPOcpo-advisor
Growth/MarketingCMOcmo-advisor
EngineeringCTOcto-advisor
Team/PeopleCHROchro-advisor
Risk/SecurityCISOciso-advisor
Strategic OutlookCEOceo-advisor

Output Artifacts

RequestDeliverable
"Prepare the board deck"Complete deck outline with section owners and data requirements
"Monthly investor update"Condensed update: metrics, highlights, risks, asks
"Help with the narrative"4-act narrative structure with key messages
"Deliver bad news"SOUF framework applied to specific situation
"Fundraising deck"Vision-led deck with traction, team, market, ask
"Review my board deck"Critique against best practices, identify gaps

Tool Reference

deck_structure_validator.py

Validates board deck completeness against best-practice section requirements.

# Validate with demo data
python scripts/deck_structure_validator.py

# Validate specific deck type with slide count
python scripts/deck_structure_validator.py --type quarterly --slides 24

# Validate with section list
python scripts/deck_structure_validator.py --sections executive_summary metrics_dashboard financial_update

# Validate from JSON file
python scripts/deck_structure_validator.py --input deck.json

# JSON output
python scripts/deck_structure_validator.py --input deck.json --json

metrics_dashboard_generator.py

Generates formatted board-ready metrics dashboards with RAG status and trends.

# Generate demo dashboard
python scripts/metrics_dashboard_generator.py

# From JSON metrics file
python scripts/metrics_dashboard_generator.py --input metrics.json

# From CSV file
python scripts/metrics_dashboard_generator.py --csv metrics.csv

# JSON output
python scripts/metrics_dashboard_generator.py --json

board_prep_checklist.py

Generates T-minus timeline checklists for board meeting preparation.

# Generate checklist for meeting 14 days out
python scripts/board_prep_checklist.py

# Specific meeting date with completed tasks
python scripts/board_prep_checklist.py --meeting-date 2026-04-15 --completed agenda_set topics_confirmed

# List all task IDs
python scripts/board_prep_checklist.py --list-tasks

# JSON output
python scripts/board_prep_checklist.py --meeting-date 2026-04-15 --json

Troubleshooting

ProblemLikely CauseFix
Board members ask basic questions answered in the deckDeck not sent far enough in advance or not self-explanatorySend 48+ hours ahead with a 3-takeaway cover note; ensure deck reads standalone
Financial numbers don't match across sectionsNo CFO cross-validation stepAdd T-5 day CFO validation checkpoint; single source of truth for all metrics
Meeting runs over time on early sectionsToo much detail in presenter slides, no time boxingEnforce max 6 lines per slide; use speaker notes for depth; assign timekeeper
Board members surprised by bad newsInformation not previewed in 1:1 pre-callsCEO pre-briefs each board member on material issues before the meeting
Asks section produces no follow-throughAsks are vague ("any help appreciated")Make asks specific, named, and actionable ("3 warm intros to Series B CFOs")
Same deck format for 4+ quarters with no improvementNo post-meeting feedback loopRate deck effectiveness at meeting end; iterate one section per quarter
Appendix never referencedAppendix is stale or not relevant to current agendaUpdate appendix before every meeting; remove data nobody has asked about in 2+ quarters

Success Criteria

  • Board members report reading the deck in advance in 80%+ of meetings (measured by pre-meeting questions received)
  • Meeting stays within time allocation with 70%+ of time on strategic discussion, not status updates
  • Every board meeting produces at least 2 logged decisions with named owners and deadlines
  • Bad news is never a surprise in the meeting -- all material issues previewed via 1:1 pre-calls
  • Board NPS (informal quarterly check) scores 8+/10 on meeting usefulness
  • Deck assembly completes by T-2 days with zero last-minute scrambles in 90%+ of quarters
  • Action items from previous meeting have 80%+ completion rate reported at the next meeting

Scope & Limitations

In Scope: Board deck structure, section templates, narrative frameworks, bad news delivery, metrics dashboards, deck assembly workflows, board prep checklists, quality validation.

Out of Scope: Actual financial data collection, slide design/visual formatting, board member relationship management, legal governance requirements, proxy statement preparation, regulatory filings.

Limitations: This skill provides structure and process but cannot replace the judgment required for crafting board narratives. The deck structure validator checks completeness, not quality of content. Metrics dashboard tools calculate RAG status from provided data but do not source live metrics.


Integration Points

SkillIntegration
ceo-advisorExecutive summary and strategic outlook sections; overall narrative direction
cfo-advisorFinancial update section; all numbers validated through CFO tools
cro-advisorRevenue and pipeline section; ARR waterfall and forecast confidence
cmo-advisorGrowth/marketing section; CAC by channel, marketing ROI data
chro-advisorTeam/people section; headcount, attrition, engagement metrics
ciso-advisorRisk/security section; security posture, compliance status
board-meetingDeck feeds into the 6-phase board meeting protocol
chief-of-staffPrep checklist coordination; section owner orchestration
company-osScorecard metrics flow directly into the metrics dashboard section

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.87%
按下载量换算158

Claude

29.45%
按下载量换算137

Cursor

17.48%
按下载量换算81

Gemini CLI

9.56%
按下载量换算45

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

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

安装前确认

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

来源信息

继续浏览同类 Skills