New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Build the storyline and slide structure

Board Deck Narrative Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Board Deck Narrative Skill cover

Build the storyline and slide structure for a board presentation. Use when asked to create a board deck, board presentation narrative, board meeting slides, or quarterly board update.

---
name: board-deck-narrative
description: "Build the storyline and slide structure for a board presentation. Use when asked to create a board deck, board presentation narrative, board meeting slides, or quarterly board update. Produces a complete slide-by-slide structure with narrative beats, talking points, and slide content guidance."
---

# Board Deck Narrative Skill

This skill builds the complete narrative and slide structure for a board presentation — from opening framing to closing asks. It produces slide-by-slide content guidance, not just a list of topics.

## Required Inputs

Ask the user for these if not provided:
- **Company stage and context** (Seed / Series A / Growth — and where you are in the year)
- **Board meeting type** (Regular quarterly / Annual / Special / Fundraise-related)
- **Key themes for this meeting** (e.g. strong growth quarter / pivoting strategy / hiring challenge / fundraise update)
- **Key metrics to feature**
- **Decisions needed from the board** (if any)
- **Time available** (e.g. 60 min / 90 min)

Overview

This skill builds the complete narrative and slide structure for a board presentation — from opening framing to closing asks. It produces slide-by-slide content guidance, not just a list of topics.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill board-deck-narrative -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/board-deck-narrative
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/c846014019b21d1f0690/board-deck-narrative.zip" -OutFile "$env:TEMP\board-deck-narrative.zip"; Expand-Archive "$env:TEMP\board-deck-narrative.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md7.3 KB
  • references/1 file · 2.1 KB
Read the files here
mohitagw15856/f6ca7932 files
SKILL.md
Show the full text170 lines

Board Deck Narrative Skill

This skill builds the complete narrative and slide structure for a board presentation — from opening framing to closing asks. It produces slide-by-slide content guidance, not just a list of topics.

Required Inputs

Ask the user for these if not provided:

  • Company stage and context (Seed / Series A / Growth — and where you are in the year)
  • Board meeting type (Regular quarterly / Annual / Special / Fundraise-related)
  • Key themes for this meeting (e.g. strong growth quarter / pivoting strategy / hiring challenge / fundraise update)
  • Key metrics to feature
  • Decisions needed from the board (if any)
  • Time available (e.g. 60 min / 90 min)
  • Audience (investors only / investors + independent directors / mixed)

Output Structure


Board Deck Narrative: [Company] — [Quarter/Period]

Meeting type: [Regular quarterly / Special] Time: [X minutes] Narrative theme: [The one-sentence story of this quarter — e.g. "We hit our revenue target, but activation is the problem we need to solve together."]


Opening Frame (Slide 1–2)

Slide 1: Title

  • Company name, quarter, date
  • One-sentence framing of the meeting's narrative arc

Slide 2: Agenda

  • List of sections + time allocation
  • Flag which sections need board input vs. are informational

Presenter note: Board members are busy. Tell them in the first 2 minutes what you need from them today. It changes how they listen.


Business Performance (Slides 3–6, ~15 min)

Slide 3: Scorecard / KPI Dashboard

  • Content: Key metrics vs. targets for the quarter. No more than 6 metrics.
  • Format: Traffic-light table (Green / Amber / Red against plan)
  • Narrative: [1–2 sentences — the headline story of the quarter in numbers]
  • Don't hide reds. Boards lose trust when they discover hidden problems later.

Slide 4: Revenue / Growth Deep Dive

  • Content: Revenue breakdown by segment, cohort retention, growth drivers
  • Key message: [What the data shows about the health of growth]
  • Call out: [Any trend that needs board context or discussion]

Slide 5: Unit Economics

  • Content: CAC, LTV, payback period, gross margin — vs. last quarter and vs. plan
  • Flag: Any metric moving in the wrong direction and what's causing it

Slide 6: Operational Highlights

  • Content: 3–5 bullet points of the most significant things that happened this quarter
  • Format: Each bullet = outcome, not activity. ("Signed 3 enterprise contracts worth £400K ARR" not "Continued enterprise sales motion")

Strategic Update (Slides 7–9, ~15 min)

Slide 7: Strategy Snapshot

  • Content: Where you said you'd be vs. where you are against the annual plan
  • Narrative: [Honest assessment — what's on track, what's shifted and why]

Slide 8: Key Strategic Decision or Update

  • Content: The one strategic topic that most needs board input this meeting
  • Format: Context → Options considered → Recommendation → Question for board
  • This is the highest-value 10 minutes of the meeting. Frame it as a real question.

Slide 9: Product & Roadmap (if relevant)

  • Content: Top 3 product bets this quarter — what shipped, what's coming, why these bets
  • Tailored for: What the board needs to understand to support strategic decisions, not a sprint review

People & Organisation (Slide 10, ~5 min)

Slide 10: Team Update

  • Content: Headcount (start vs. end of quarter), key hires made, open roles, any org changes
  • Flag: Any people risks or leadership gaps the board should know about
  • Don't skip this slide. Board members often have network value here.

Financial Update (Slides 11–12, ~10 min)

Slide 11: P&L Summary

  • Content: Revenue, gross margin, opex by category, EBITDA/net burn — actual vs. budget
  • Include: Year-to-date vs. annual plan

Slide 12: Cash & Runway

  • Content: Cash on hand, monthly burn rate, runway at current burn
  • Include: Scenario if burn increases (e.g. key hire made), scenario if growth accelerates
  • Flag immediately: If runway is < 18 months — this needs board awareness and planning

Closing & Asks (Slides 13–14, ~10 min)

Slide 13: Priorities for Next Quarter

  • Content: Top 3–5 priorities and what success looks like for each
  • Format: Priority | What we're doing | How we'll know it worked
  • Keeps board accountability consistent across meetings

Slide 14: Board Asks

  • Content: Specific things you need from board members before next meeting
  • Format: Each ask = specific, named if possible ("Looking for an intro to [Company] — [Board member X], do you have a connection?")
  • A board meeting without specific asks is a missed opportunity

Appendix (Optional)

  • Detailed cohort analysis
  • Competitive landscape update
  • Full P&L
  • Team org chart
  • Any supporting data referenced in the main deck

Appendix slides are available but not presented. Board members who want detail can ask.


Narrative Principles

  • Lead with honesty. If it was a hard quarter, say so in the first slide. Don't bury bad news after the wins.
  • One slide = one idea. If a slide has two messages, split it.
  • Fewer slides, more depth. A 14-slide deck presented well beats a 35-slide deck rushed through.
  • Every slide has a "so what." A slide that just shows data without a takeaway wastes board time.
  • Leave time for discussion. Board value is in the conversation, not the presentation. Aim to spend 40% of the meeting presenting and 60% in discussion.

Deeper Materials

Quality Checks

  • Opening frame states the meeting's narrative theme
  • Scorecard slide uses traffic-light format (not just green metrics)
  • Strategic decision slide frames a real question for the board
  • Financial slide includes runway explicitly
  • Board asks are specific and actionable
  • Deck is ≤ 15 slides (excluding appendix)

Anti-Patterns

  • Do not bury bad news after slides full of good news — boards lose trust when they discover problems were de-emphasised; lead with the honest narrative
  • Do not include slides without a "so what" — a chart that shows data without a takeaway wastes board time and signals the presenter hasn't done the analysis
  • Do not exceed 15 slides in the main deck — a longer deck usually means the presenter hasn't decided what matters most
  • Do not attend a board meeting without at least one specific ask — a board meeting with no asks is a missed opportunity to leverage the room
  • Do not report metrics without comparing them to plan or a prior period — a metric shown in isolation gives the board no basis for judgement

Example Trigger Phrases

  • "Build a board deck structure for our Q[N] board meeting"
  • "Help me create the narrative for our board presentation"
  • "Write the slide structure for our annual board review"
  • "Design a board deck for [specific context — e.g. fundraise update]"
1---
2name: board-deck-narrative
3description: "Build the storyline and slide structure for a board presentation. Use when asked to create a board deck, board presentation narrative, board meeting slides, or quarterly board update. Produces a complete slide-by-slide structure with narrative beats, talking points, and slide content guidance."
4---
5 
6# Board Deck Narrative Skill
7 
8This skill builds the complete narrative and slide structure for a board presentation — from opening framing to closing asks. It produces slide-by-slide content guidance, not just a list of topics.
9 
10## Required Inputs
11 
12Ask the user for these if not provided:
13- **Company stage and context** (Seed / Series A / Growth — and where you are in the year)
14- **Board meeting type** (Regular quarterly / Annual / Special / Fundraise-related)
15- **Key themes for this meeting** (e.g. strong growth quarter / pivoting strategy / hiring challenge / fundraise update)
16- **Key metrics to feature**
17- **Decisions needed from the board** (if any)
18- **Time available** (e.g. 60 min / 90 min)
19- **Audience** (investors only / investors + independent directors / mixed)
20 
21## Output Structure
22 
23---
24 
25# Board Deck Narrative: [Company] — [Quarter/Period]
26 
27**Meeting type:** [Regular quarterly / Special]
28**Time:** [X minutes]
29**Narrative theme:** [The one-sentence story of this quarter — e.g. "We hit our revenue target, but activation is the problem we need to solve together."]
30 
31---
32 
33## Opening Frame (Slide 1–2)
34 
35**Slide 1: Title**
36- Company name, quarter, date
37- One-sentence framing of the meeting's narrative arc
38 
39**Slide 2: Agenda**
40- List of sections + time allocation
41- Flag which sections need board input vs. are informational
42 
43*Presenter note: Board members are busy. Tell them in the first 2 minutes what you need from them today. It changes how they listen.*
44 
45---
46 
47## Business Performance (Slides 3–6, ~15 min)
48 
49**Slide 3: Scorecard / KPI Dashboard**
50- Content: Key metrics vs. targets for the quarter. No more than 6 metrics.
51- Format: Traffic-light table (Green / Amber / Red against plan)
52- Narrative: [1–2 sentences — the headline story of the quarter in numbers]
53- *Don't hide reds. Boards lose trust when they discover hidden problems later.*
54 
55**Slide 4: Revenue / Growth Deep Dive**
56- Content: Revenue breakdown by segment, cohort retention, growth drivers
57- Key message: [What the data shows about the health of growth]
58- Call out: [Any trend that needs board context or discussion]
59 
60**Slide 5: Unit Economics**
61- Content: CAC, LTV, payback period, gross margin — vs. last quarter and vs. plan
62- Flag: Any metric moving in the wrong direction and what's causing it
63 
64**Slide 6: Operational Highlights**
65- Content: 3–5 bullet points of the most significant things that happened this quarter
66- Format: Each bullet = outcome, not activity. ("Signed 3 enterprise contracts worth £400K ARR" not "Continued enterprise sales motion")
67 
68---
69 
70## Strategic Update (Slides 7–9, ~15 min)
71 
72**Slide 7: Strategy Snapshot**
73- Content: Where you said you'd be vs. where you are against the annual plan
74- Narrative: [Honest assessment — what's on track, what's shifted and why]
75 
76**Slide 8: Key Strategic Decision or Update**
77- Content: The one strategic topic that most needs board input this meeting
78- Format: Context → Options considered → Recommendation → Question for board
79- *This is the highest-value 10 minutes of the meeting. Frame it as a real question.*
80 
81**Slide 9: Product & Roadmap (if relevant)**
82- Content: Top 3 product bets this quarter — what shipped, what's coming, why these bets
83- Tailored for: What the board needs to understand to support strategic decisions, not a sprint review
84 
85---
86 
87## People & Organisation (Slide 10, ~5 min)
88 
89**Slide 10: Team Update**
90- Content: Headcount (start vs. end of quarter), key hires made, open roles, any org changes
91- Flag: Any people risks or leadership gaps the board should know about
92- *Don't skip this slide. Board members often have network value here.*
93 
94---
95 
96## Financial Update (Slides 11–12, ~10 min)
97 
98**Slide 11: P&L Summary**
99- Content: Revenue, gross margin, opex by category, EBITDA/net burn — actual vs. budget
100- Include: Year-to-date vs. annual plan
101 
102**Slide 12: Cash & Runway**
103- Content: Cash on hand, monthly burn rate, runway at current burn
104- Include: Scenario if burn increases (e.g. key hire made), scenario if growth accelerates
105- Flag immediately: If runway is < 18 months — this needs board awareness and planning
106 
107---
108 
109## Closing & Asks (Slides 13–14, ~10 min)
110 
111**Slide 13: Priorities for Next Quarter**
112- Content: Top 3–5 priorities and what success looks like for each
113- Format: Priority | What we're doing | How we'll know it worked
114- *Keeps board accountability consistent across meetings*
115 
116**Slide 14: Board Asks**
117- Content: Specific things you need from board members before next meeting
118- Format: Each ask = specific, named if possible ("Looking for an intro to [Company] — [Board member X], do you have a connection?")
119- *A board meeting without specific asks is a missed opportunity*
120 
121---
122 
123## Appendix (Optional)
124 
125- Detailed cohort analysis
126- Competitive landscape update
127- Full P&L
128- Team org chart
129- Any supporting data referenced in the main deck
130 
131*Appendix slides are available but not presented. Board members who want detail can ask.*
132 
133---
134 
135## Narrative Principles
136 
137- **Lead with honesty.** If it was a hard quarter, say so in the first slide. Don't bury bad news after the wins.
138- **One slide = one idea.** If a slide has two messages, split it.
139- **Fewer slides, more depth.** A 14-slide deck presented well beats a 35-slide deck rushed through.
140- **Every slide has a "so what."** A slide that just shows data without a takeaway wastes board time.
141- **Leave time for discussion.** Board value is in the conversation, not the presentation. Aim to spend 40% of the meeting presenting and 60% in discussion.
142 
143## Deeper Materials
144 
145- [`references/what-boards-actually-read.md`](references/what-boards-actually-read.md) — the pre-read reality, in-room dynamics, and the asks discipline
146 
147## Quality Checks
148 
149- [ ] Opening frame states the meeting's narrative theme
150- [ ] Scorecard slide uses traffic-light format (not just green metrics)
151- [ ] Strategic decision slide frames a real question for the board
152- [ ] Financial slide includes runway explicitly
153- [ ] Board asks are specific and actionable
154- [ ] Deck is ≤ 15 slides (excluding appendix)
155 
156## Anti-Patterns
157 
158- [ ] Do not bury bad news after slides full of good news — boards lose trust when they discover problems were de-emphasised; lead with the honest narrative
159- [ ] Do not include slides without a "so what" — a chart that shows data without a takeaway wastes board time and signals the presenter hasn't done the analysis
160- [ ] Do not exceed 15 slides in the main deck — a longer deck usually means the presenter hasn't decided what matters most
161- [ ] Do not attend a board meeting without at least one specific ask — a board meeting with no asks is a missed opportunity to leverage the room
162- [ ] Do not report metrics without comparing them to plan or a prior period — a metric shown in isolation gives the board no basis for judgement
163 
164## Example Trigger Phrases
165 
166- "Build a board deck structure for our Q[N] board meeting"
167- "Help me create the narrative for our board presentation"
168- "Write the slide structure for our annual board review"
169- "Design a board deck for [specific context — e.g. fundraise update]"
170 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with board-deck-narrative

Board Deck Narrative Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Board Deck Narrative Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Board Deck Narrative Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Board Deck Narrative Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillCreate stunning, animation-rich HTML presentationsFrontend slideszarazhangrui/frontend-slides · by zarazhangruiCreate stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.★ 30.3k GitHub starsSkillCreate professional, dark-themed SVG diagrams of any typeDiagram GeneratorJimLiu/baoyu-skills · by JimLiuCreate professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system, process flow, data flow, component relationship, network topology, decision tree, org chart, state machine, or any visual representation of structure/logic/process. Also trigger when the user says "画个图" "画一个架构图" "diagram" "flowchart" "sequence diagram" "draw me a ..." or uploads content and asks to visualize it. Output is always a standalone .svg file.★ 26.6k GitHub starsSkillGenerate self-contained HTML visual explanations for systemsVisual explainernicobailon/visual-explainer · by nicobailonGenerate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, animated explainers, and other visual explanations.★ 10.2k GitHub starsSkillHTML PPT Studio — author professional static HTMLhtml-ppt — HTML PPT Studiolewislulu/html-ppt-skill · by lewisluluHTML PPT Studio — author professional static HTML presentations in many styles, layouts, and animations, all driven by templates. Use when the user asks for a presentation, PPT, slides, keynote, deck, slideshow, "幻灯片", "演讲稿", "做一份 PPT", "做一份 slides", a reveal-style HTML deck, a 小红书 图文, or any kind of multi-slide pitch/report/sharing document that should look tasteful and be usable with keyboard navigation. Triggers include keywords like "presentation", "ppt", "slides", "deck", "keynote", "reveal", "slideshow", "幻灯片", "演讲稿", "分享稿", "小红书图文", "talk slides", "pitch deck", "tech sharing", "technical presentation".★ 8.6k GitHub starsSkillProfessional logo and brand-mark designLogo designkaankiziltug/logo-design-skill · by kaankiziltugProfessional logo and brand-mark design, from brief to production files. Guides discovery and the design brief, concept generation, choosing a mark type (wordmark, monogram, letterform, pictorial, abstract, emblem, mascot, combination), building clean geometric SVG logos, optical refinement, colour and typography, testing (16 px, one-colour, reversed, shelf test), client presentation, delivery variants and brand guidelines. Includes a searchable library of 1,400+ real-world SVG logos classified by type, technique, geometry and industry, plus scripts that audit SVGs and generate test sheets, presentation boards and export variants. Use this skill whenever the user wants a logo, logotype, wordmark, monogram, brand mark, symbol, app icon or favicon designed, redesigned, refreshed, critiqued or compared; asks for logo ideas or concepts; needs a design brief, logo guidelines, lockups or an identity system; or mentions branding a new company, product, app or project — even if they don't say the word "logo".★ 2.8k GitHub starsSkillDraws a code change or partPR Lenscoldteadotai/pr-lens · by coldteadotaiWHAT: Draws a code change or part of a codebase as an animated architecture or data-flow diagram, on its own or in a pull request. WHEN: asked to diagram, visualise or explain a change or a system, or when a pull request should carry a diagram. KEYWORDS: PR Lens, diagram, architecture, data flow, visualise, visualize, pull request★ 1.9k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars