Gtm Board And Investor Communication
github/awesome-copilot
Board meeting preparation, investor updates, and executive communication.
Assembles board and investor update decks by pulling perspectives from all C-suite roles.
Install Board Deck Builder
$ npx skills add borghei/Claude-Skills --skill board-deck-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills board-deck-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-advisor/board-deck-builder .claude/skills/board-deck-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "board-deck-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/board-deck-builder into .claude/skills/board-deck-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-deck-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/board-deck-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill board-deck-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills board-deck-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-advisor/board-deck-builder .agents/skills/board-deck-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "board-deck-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/board-deck-builder into .agents/skills/board-deck-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-deck-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill board-deck-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills board-deck-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-advisor/board-deck-builder .cursor/skills/board-deck-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "board-deck-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/board-deck-builder into .cursor/skills/board-deck-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-deck-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path c-level-advisor/board-deck-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill board-deck-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills board-deck-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-advisor/board-deck-builder .gemini/skills/board-deck-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "board-deck-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/board-deck-builder into .gemini/skills/board-deck-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-deck-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills board-deck-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill board-deck-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-advisor/board-deck-builder .github/skills/board-deck-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "board-deck-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/board-deck-builder into .github/skills/board-deck-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-deck-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill board-deck-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills board-deck-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-advisor/board-deck-builder .opencode/skills/board-deck-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "board-deck-builder" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/board-deck-builder into .opencode/skills/board-deck-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "board-deck-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
board-deck-builder- GitHub stars
- 874
- Token cost
- ~4.5k tokens
- SKILL.md length
- 1,927 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 364
- Repo updated
- First seen
- Licence
- MIT
At a glance
Assembles board and investor update decks by pulling perspectives from all C-suite roles.
- Preparing board meetings
- SKILL.md covers Keywords, Clarify First, Deck Types and Structure and Standard Board Deck (Section…, plus 9 more sections
- Runs Python scripts from its folder; calls python
- Investor updates
What it does
Board Deck Builder is an agent skill from borghei/Claude-Skills. Assembles board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives.
Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/board_prep_checklist.py`, `scripts/deck_structure_validator.py` and `scripts/metrics_dashboard_generator.py`).
It sits in Business, Finance & HR, covering Fundraising and pitch decks, OKRs and executive reporting and Customer success. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Preparing board meetings
- Investor updates
- Quarterly business reviews
- Fundraising narratives
Example prompts
- “Use the board-deck-builder skill to assemble board and investor update decks by pulling perspectives from all C-suite roles”
- “/board-deck-builder”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Board Deck Builder loads about 4.5k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 1,927 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 1,927 words, ~4,516 tokens.
Download SKILL.mdSave it as
.claude/skills/board-deck-builder/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- board-deck-builder
- description
- Assembles board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives.
- license
- MIT + Commons Clause
- metadata.version
- 2.0.0
- metadata.author
- borghei
- metadata.category
- c-level
- metadata.domain
- board-governance
- metadata.updated
- 2026-03-09
- metadata.frameworks
- deck-structure, narrative-framework, bad-news-delivery, section-templates, fundraising-format
- metadata.triggers
- board deck, investor update, board meeting, board pack, investor relations, quarterly review, board presentation, fundraising deck, investor deck, board…
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
Clarify First
Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Deck type and audience (quarterly board, monthly update, fundraising, emergency) — sets slide count, structure, and which sections appear
- The headline message this period (beat plan / missed plan / need a decision) — drives the opening frame and whether the SOUF bad-news structure is needed
- Which metrics the board actually tracks (and their targets) — the metrics dashboard should show only these, with RAG status against targets
- Specific asks or decisions needed from the board — the asks section is the highest-value slide and must be concrete and owner-assigned
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Deck Types and Structure
Deck Type Selection
| Type | When | Slide Count | Sent in Advance | Key Section |
|---|---|---|---|---|
| Quarterly Board Deck | Standard board meeting | 20-30 slides | 48 hours ahead | Full deck below |
| Monthly Update | Early-stage boards | 8-12 slides | 24 hours ahead | Metrics + risks |
| Fundraising Deck | Active fundraise | 12-15 slides | During meeting | Vision + traction |
| Emergency/Ad-hoc | Crisis or major decision | 5-8 slides | Depends | Situation + options |
Standard Board Deck (Section by Section)
Section 1: Executive Summary (CEO)
Three sentences. No more. No less.
| Sentence | Purpose | Example |
|---|---|---|
| 1 | State of the business | "We closed Q3 at $2.4M ARR, up 22% QoQ" |
| 2 | Biggest development this period | "Signed our largest enterprise contract ($180K ACV)" |
| 3 | Forward-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.
| Metric | This Period | Last Period | Target | Status | Trend |
|---|---|---|---|---|---|
| ARR | $2.4M | $1.97M | $2.3M | [G] | Up |
| MoM Growth | 8.1% | 7.2% | 7.5% | [G] | Up |
| Burn Multiple | 1.8x | 2.1x | < 2x | [G] | Improving |
| NRR | 112% | 108% | > 110% | [G] | Up |
| CAC Payback | 11 mo | 14 mo | < 12 mo | [G] | Improving |
| Headcount | 24 | 21 | 25 | [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)
| Component | Include | Format |
|---|---|---|
| P&L Summary | Revenue, COGS, Gross Margin, OpEx, Net Burn | Table with variance column |
| Cash Position | Current balance + runway in months | Single number, bold |
| Burn Multiple Trend | 3-quarter trend | Line chart |
| Variance to Plan | Each line item vs. budget | Table with one-sentence explanations |
| Forecast Update | Next quarter projections | Conservative, 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)
| Component | Include | Format |
|---|---|---|
| ARR Waterfall | Opening -> New -> Expansion -> Contraction -> Churn -> Closing | Waterfall chart |
| NRR and Logo Churn | Current + 4-quarter trend | Table + trend line |
| Pipeline by Stage | Dollar amounts, not just counts | Funnel visualization |
| Forecast | Next quarter with confidence level | "High confidence $2.6M, upside to $2.9M" |
| Top 3 Deals | Name, amount, close date, risk | Table |
Rule: Forecast MUST include a confidence level. "We expect $2.8M" is weak.
Section 5: Product Update (CPO)
| Component | Include | Format |
|---|---|---|
| Shipped This Quarter | 3-5 items with user impact | Bullet list |
| Shipping Next Quarter | 3-5 items with target dates | Bullet list |
| PMF Signals | NPS trend, DAU/MAU, feature adoption | Metrics table |
| Key Learning | One insight from customer research | Narrative paragraph |
Rule: No feature lists. Only features with evidence of user impact.
Section 6: Growth and Marketing (CMO)
| Component | Include |
|---|---|
| CAC by Channel | Table with efficiency trend |
| Pipeline Contribution | $ by channel |
| What's Working | Specific channels/campaigns with data |
| What's Being Cut | Underperforming channels |
| What's Being Tested | New experiments with hypothesis |
Section 7: Engineering and Technical (CTO)
| Component | Include |
|---|---|
| Delivery Velocity | 4-quarter trend |
| Tech Debt Ratio | Current + plan to address |
| Infrastructure | Uptime, incidents, cost trend |
| Security Posture | One 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)
| Component | Include |
|---|---|
| Headcount | Actual vs. plan |
| Hiring | Offers out, pipeline, time-to-fill trend |
| Attrition | Regrettable vs. non-regrettable |
| Engagement | Latest survey score and trend |
| Notable | Key hires, key departures, key open roles |
Section 9: Risk and Security (CISO)
| Component | Include |
|---|---|
| Security Posture | Status of critical controls |
| Compliance | Certifications in progress, deadlines |
| Incidents | This quarter (if any): impact, resolution, prevention |
| Top 3 Risks | Risk description + mitigation status |
Section 10: Strategic Outlook (CEO)
| Component | Include |
|---|---|
| Next Quarter Priorities | 3-5 items, ranked by importance |
| Board Decisions Needed | Specific votes or approvals |
| Asks | Specific, 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 actionsThis 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 Opening | Bad 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
| Step | What | Example |
|---|---|---|
| State | State it plainly | "We missed Q3 ARR target by $300K (12% gap)" |
| Own | Own the cause | "Primary driver: longer enterprise sales cycle than modeled" |
| Understand | Show you understand it | "Analyzed 8 stalled deals; pattern is procurement delays" |
| Fix | Present the fix | "Three changes: [specific, dated], revised Q4 target: $2.6M" |
Bad News Anti-Patterns
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Leading with good news to soften | Boards notice and distrust framing | Lead with the most important thing |
| "Market conditions" as cause | That is context, not a cause | Name specific, controllable causes |
| Fix without data | Board does not trust unfounded fixes | Show analysis behind the fix |
| Revised forecast without assumptions | Looks like guessing | Show bottom-up build |
Common Board Deck Mistakes
| Mistake | Fix |
|---|---|
| Too many slides (> 25) | Cut ruthlessly. If you can not explain it, the slide is wrong. |
| Metrics without targets | Every metric needs a target and a status indicator |
| No narrative | Data without story forces boards to draw 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 a one-sentence cause |
| Stale appendix | Appendix is only useful if current |
| Designed for reader, not room | Decks are presented -- they must work spoken aloud |
| Inconsistent formatting | Use one template, one color scheme, one font |
| Too much text per slide | Max 6 lines per slide. Use speaker notes for detail. |
Show full SKILL.md (721 more words)Show less
Cadence Notes
| Type | Timing | Length | Advance Send |
|---|---|---|---|
| Quarterly (standard) | 48 hours before meeting | 20-30 slides | 48 hours |
| Monthly (early-stage) | 24 hours before meeting | 8-12 slides | 24 hours |
| Fundraising | In the meeting | 12-15 slides | Sometimes 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:
| Section | Owner | Reference Skill |
|---|---|---|
| Executive Summary | CEO | ceo-advisor |
| Metrics Dashboard | COO | coo-advisor |
| Financial Update | CFO | cfo-advisor |
| Revenue/Pipeline | CRO | cro-advisor |
| Product Update | CPO | cpo-advisor |
| Growth/Marketing | CMO | cmo-advisor |
| Engineering | CTO | cto-advisor |
| Team/People | CHRO | chro-advisor |
| Risk/Security | CISO | ciso-advisor |
| Strategic Outlook | CEO | ceo-advisor |
Output Artifacts
| Request | Deliverable |
|---|---|
| "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 --jsonmetrics_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 --jsonboard_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 --jsonTroubleshooting
| Problem | Likely Cause | Fix |
|---|---|---|
| Board members ask basic questions answered in the deck | Deck not sent far enough in advance or not self-explanatory | Send 48+ hours ahead with a 3-takeaway cover note; ensure deck reads standalone |
| Financial numbers don't match across sections | No CFO cross-validation step | Add T-5 day CFO validation checkpoint; single source of truth for all metrics |
| Meeting runs over time on early sections | Too much detail in presenter slides, no time boxing | Enforce max 6 lines per slide; use speaker notes for depth; assign timekeeper |
| Board members surprised by bad news | Information not previewed in 1:1 pre-calls | CEO pre-briefs each board member on material issues before the meeting |
| Asks section produces no follow-through | Asks 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 improvement | No post-meeting feedback loop | Rate deck effectiveness at meeting end; iterate one section per quarter |
| Appendix never referenced | Appendix is stale or not relevant to current agenda | Update 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
| Skill | Integration |
|---|---|
ceo-advisor | Executive summary and strategic outlook sections; overall narrative direction |
cfo-advisor | Financial update section; all numbers validated through CFO tools |
cro-advisor | Revenue and pipeline section; ARR waterfall and forecast confidence |
cmo-advisor | Growth/marketing section; CAC by channel, marketing ROI data |
chro-advisor | Team/people section; headcount, attrition, engagement metrics |
ciso-advisor | Risk/security section; security posture, compliance status |
board-meeting | Deck feeds into the 6-phase board meeting protocol |
chief-of-staff | Prep checklist coordination; section owner orchestration |
company-os | Scorecard metrics flow directly into the metrics dashboard section |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in c-level-advisor/board-deck-builder of borghei/Claude-Skills.
- SKILL.md
- scripts/board_prep_checklist.py
- scripts/deck_structure_validator.py
- scripts/metrics_dashboard_generator.py
Open the folder on GitHubat commit c9a1487
Compare with similar skills
Board Deck Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Board Deck Builder this skillborghei/Claude-Skills | 874 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Gtm Board And Investor Communicationgithub/awesome-copilot | 40k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Board Deck Builderalirezarezvani/claude-skills | 28k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Replit Decksanqiufong/slides-from-anything | 132 | 1 repos | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Board Updateshawnpang/startup-founder-skills | 337 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Process Mapperalirezarezvani/claude-skills | 28k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Board Deck Builder
alirezarezvani/claude-skills
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles.
Replit Deck
sanqiufong/slides-from-anything
Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery.
Board Update
shawnpang/startup-founder-skills
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
Process Mapper
alirezarezvani/claude-skills
A skill your agent uses when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff…
Security Comms
briiirussell/cybersecurity-skills
Translate technical security work into the language of non-security audiences — board, executives, engineering, customer success, customers, legal, procurement, sales.
More from borghei/Claude-Skills
All 364 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Board Deck Builder
What does Board Deck Builder do?
Assembles board and investor update decks by pulling perspectives from all C-suite roles. Board Deck Builder is an agent skill from borghei/Claude-Skills. Assembles board and investor update decks by pulling perspectives from all C-suite roles.
When should I use Board Deck Builder?
Board Deck Builder fits situations like: preparing board meetings; investor updates; quarterly business reviews; fundraising narratives.
How do I install Board Deck Builder in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill board-deck-builder -a claude-code`. Or copy the skill folder (c-level-advisor/board-deck-builder in borghei/Claude-Skills) into .claude/skills/board-deck-builder in your project. Claude Code loads it when a task matches its description.
How do I install Board Deck Builder in Codex?
Run `npx skills add borghei/Claude-Skills --skill board-deck-builder -a codex`. Or copy the skill folder (c-level-advisor/board-deck-builder in borghei/Claude-Skills) into .agents/skills/board-deck-builder in your project. Codex loads it when a task matches its description.
Can I use Board Deck Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill board-deck-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/board-deck-builder, .gemini/skills/board-deck-builder, .github/skills/board-deck-builder and .opencode/skills/board-deck-builder in your project.
What does Board Deck Builder need to run?
Going by SKILL.md and its folder, Board Deck Builder needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Board Deck Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Board Deck Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Board Deck Builder use?
Board Deck Builder is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Board Deck Builder use?
About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Board Deck Builder?
Skills that share tags, products or a category with Board Deck Builder: Gtm Board And Investor Communication (github/awesome-copilot, 40k stars), Board Deck Builder (alirezarezvani/claude-skills, 28k stars), Replit Deck (sanqiufong/slides-from-anything, 132 stars) and Board Update (shawnpang/startup-founder-skills, 337 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Board Deck Builder?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.