board-deck-builder – skill Khác cho agent AI
Tổng hợp bộ slide hoàn chỉnh cho hội đồng quản trị và nhà đầu tư bằng cách lấy quan điểm từ tất cả vai trò C-suite. Dùng khi chuẩn bị họp hội đồng, cập nhật cho nhà đầu tư, đánh giá kinh doanh hàng quý hoặc câu chuyện gọi vốn. Bao gồm cấu trúc, khung kể chuyện, cách truyền đạt tin xấu và các lỗi thường gặp.
Cài skill board-deck-builder bằng một lệnh
Chọn công cụ bạn đang dùng, copy lệnh và dán vào terminal. Skill sẽ nằm trong thư mục skills của công cụ đó và sẵn sàng dùng ở phiên làm việc tiếp theo.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/board-deck-builder-96ce1.tgz | tar xz -C ~/.claude/skills
Gọi trong Claude Code: /board-deck-builder – rồi mô tả công việc bạn muốn làm.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/board-deck-builder-96ce1.tgz | tar xz -C ~/.codex/skills
Gọi trong Codex: $board-deck-builder – rồi mô tả công việc bạn muốn làm.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/board-deck-builder-96ce1.tgz | tar xz -C ~/.hermes/skills
Gọi trong Hermes Agent: /board-deck-builder – rồi mô tả công việc bạn muốn làm.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/board-deck-builder-96ce1.tgz | tar xz -C ~/.deepcode/skills
Gọi trong DeepSeek: /board-deck-builder – rồi mô tả công việc bạn muốn làm.
Nội dung SKILL.md
Nội dung SKILL.md gốc bằng tiếng Anh.
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."
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
Quick Start
Ask for a board deck in natural language, naming cadence and stage:
> "Build a quarterly board deck — we're Series A."
> "Draft a fundraising board deck for a seed-stage company."
Provide available metrics. The builder fills gaps with explicit placeholders — never invents numbers.
Deck Structure (Standard Order)
Every section follows: Headline → Data → Narrative → Ask/Next
1. Executive Summary (CEO)
3 sentences. No more.
- Sentence 1: State of the business (where we are)
- Sentence 2: Biggest thing that happened this period
- Sentence 3: Where we're going next quarter
*Bad:* "We had a good quarter with lots of progress across all areas."
*Good:* "We closed Q3 at $2.4M ARR (+22% QoQ), signed our largest enterprise contract, and enter Q4 with 14-month runway. The strategic shift to mid-market is working — ACV up 40% and sales cycle down 3 weeks. Q4 priority: close the $3M Series A and hit $2.8M ARR."
2. Key Metrics Dashboard (COO)
6-8 metrics max. Use a table.
| Metric | This Period | Last Period | Target | Status |
|--------|-------------|-------------|--------|--------|
| ARR | $2.4M | $1.97M | $2.3M | ✅ |
| MoM growth | 8.1% | 7.2% | 7.5% | ✅ |
| Burn multiple | 1.8x | 2.1x | <2x | ✅ |
| NRR | 112% | 108% | >110% | ✅ |
| CAC payback | 11 months | 14 months | <12 months | ✅ |
| Headcount | 24 | 21 | 25 | 🟡 |
Pick metrics the board actually tracks. Swap out anything they've said they don't care about.
3. Financial Update (CFO)
- P&L summary: Revenue, COGS, Gross margin, OpEx, Net burn
- Cash position and runway (months)
- Burn multiple trend (3-quarter view)
- Variance to plan (what was different and why)
- Forecast update for next quarter
One sentence on each variance. Boards hate "revenue was below target" with no explanation. Say why.
4. Revenue & Pipeline (CRO)
- ARR waterfall: starting → new → expansion → churn → ending
- NRR and logo churn rates
- Pipeline by stage (in $, not just count)
- Forecast: next quarter with confidence level
- Top 3 deals: name/amount/close date/risk
The forecast must have a confidence level. "We expect $2.8M" is weak. "High confidence $2.6M, upside to $2.9M if two late-stage deals close" is useful.
5. Product Update (CPO)
- Shipped this quarter: 3-5 bullets, user impact for each
- Shipping next quarter: 3-5 bullets with target dates
- PMF signal: NPS trend, DAU/MAU ratio, feature adoption
- One key learning from customer research
No feature lists. Only features with evidence of user impact.
6. Growth & Marketing (CMO)
- CAC by channel (table)
- Pipeline contribution by channel ($)
- Brand/awareness metrics relevant to stage (traffic, share of voice)
- What's working, what's being cut, what's being tested
7. Engineering & Technical (CTO)
- Delivery velocity trend (last 4 quarters)
- Tech debt ratio and plan
- Infrastructure: uptime, incidents, cost trend
- Security posture (one line, flag anything pending)
Keep this short unless there's a material issue. Boards don't need sprint details.
8. Team & People (CHRO)
- Headcount: actual vs plan
- Hiring: offers out, pipeline, time-to-fill trend
- Attrition: regrettable vs non-regrettable
- Engagement: last survey score, trend
- Key hires this quarter, key open roles
9. Risk & Security (CISO)
- Security posture: status of critical controls
- Compliance: certifications in progress, deadlines
- Incidents this quarter (if any): impact, resolution, prevention
- Top 3 risks and mitigation status
10. Strategic Outlook (CEO)
- Next quarter priorities: 3-5 items, ranked
- Key decisions needed from the board
- Asks: budget, introductions, advice, votes
The "asks" slide is the most important. Be specific. "We'd like 3 warm introductions to CFOs at Series B companies" beats "any help would be appreciated."
11. Appendix
- Detailed financial model
- Full pipeline data
- Cohort retention charts
- Customer case studies
- Detailed headcount breakdown
---
Narrative Framework
Boards see 10+ decks per quarter. Yours needs a through-line.
The 4-Act Structure:
1. Where we said we'd be (last quarter's targets)
2. Where we actually are (honest assessment)
3. Why the gap exists (one cause per variance, not excuses)
4. What we're doing about it (specific, dated actions)
This works for good news AND bad news. It's credible because it acknowledges reality.
Opening frame: Start with the one thing that matters most — the board should know the key message by slide 3, not slide 30.
---
Delivering Bad News
Never bury it. Boards find out eventually. Finding out late makes it worse.
Framework:
1. State it plainly — "We missed Q3 ARR target by $300K (12% gap)"
2. Own the cause — "Primary driver was longer-than-expected sales cycle in enterprise segment"
3. Show you understand it — "We analyzed 8 lost/stalled deals; the pattern is X"
4. Present the fix — "We've made 3 changes: [specific, dated changes]"
5. Update the forecast — "Revised Q4 target is $2.6M; here's the bottom-up build"
What NOT to do:
- Don't lead with good news to soften bad news — boards notice and distrust the framing
- Don't explain without owning — "market conditions" is not a cause, it's a context
- Don't present a fix without data behind it
- Don't show a revised forecast without showing your assumptions
---
Common Board Deck Mistakes
| Mistake | Fix |
|---------|-----|
| Too many slides (>25) | Cut ruthlessly — if you can't explain it in the room, the slide is wrong |
| Metrics without targets | Every metric needs a target and a status |
| No narrative | Data without story forces boards to draw their own conclusions |
| Burying bad news | Lead with it, own it, fix it |
| Vague asks | Specific, actionable, person-assigned asks only |
| No variance explanation | Every gap from target needs one-sentence cause |
| Stale appendix | Appendix is only useful if it's current |
| Designing for the reader, not the room | Decks are presented — they must work spoken aloud |
---
Cadence Notes
Quarterly (standard): Full deck, all sections, 20-30 slides. Sent 48 hours in advance.
Monthly (for early-stage): Condensed — metrics dashboard, financials, pipeline, top risks. 8-12 slides.
Fundraising: Opens with market/vision, closes with ask. See references/deck-frameworks.md for Sequoia format.
References
references/deck-frameworks.md— SaaS board pack format, Sequoia structure, investor tailoringtemplates/board-deck-template.md— fill-in template for complete board decks
Skill liên quan
- notion-knowledge-capture – Ghi lại hội thoại và quyết định thành trang Notion có cấu trúc; dùng khi biến chat hoặc…
- skill-creator – Hướng dẫn tạo skill hiệu quả. Dùng khi người dùng muốn tạo skill mới (hoặc cập nhật…
- google-dorks-catalog – Google dork độ chính xác cao để tìm cấu hình, secret và thông tin xác thực bị lộ -- đã…
- datamol – Wrapper Python bao quanh RDKit với giao diện đơn giản và mặc định hợp lý. Ưu tiên cho…
- alerting-oncall – Thiết lập quy tắc cảnh báo, cấu hình lịch trực on-call và quản lý quy trình xử lý sự cố.
- anchor-text-analyzer – Anchor Text Analyzer. Dùng khi làm việc với liên kết có anchor text và đích đến.
- angular – Chuyên gia Angular hiện đại (v20+), am hiểu sâu Signals, Standalone Components, ứng dụng…
- angular-state-management – Nắm vững quản lý state hiện đại trong Angular với Signals, NgRx và RxJS. Dùng khi thiết…