agentleFS
Sign inStart free
OneWave-AIOneWave-AI/claude-skills/board-deck-generator/SKILL.md

board-deck-generator

Skill378 starsChanged 52 days agoMITView on GitHub

Generates professional board meeting presentation content (board-deck.md) with executive summary, financials, product updates, GTM metrics, team/hiring, strategic decisions, and appendix. Supports early-stage, growth-stage, and pre-IPO formats. Use when preparing board meeting materials, quarterly board updates, or investor presentations.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provides a prior board deck, read it first to maintain continuity in metric tracking, formatting, and narrative threads.

    line 36
  2. Distinctive:

    Add analysis: explain what numbers mean, why they changed, and what to do about them.

    line 39
  3. Very specific:

    Write the completed deck to board-deck.md in the current working directory (or a user-specified path).

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Board Deck Generator

Generate institutional-quality board-deck.md content: concise, data-driven, honest about challenges, and focused on the decisions that need board input. Output must be ready for a CEO to present directly or hand to a design team for slide conversion.

Contents

  • references/document-structure.md -- The required 12-section deck structure with all tables and templates.
  • references/stage-templates.md -- Early-stage, growth-stage, and pre-IPO emphasis and per-section additions.
  • references/style-guide.md -- Formatting rules, tone and voice, quality checklist, common mistakes.
  • references/examples.md -- A fully worked board ask.

Inputs

Collect from the user. If critical inputs are missing, ask before generating. For non-critical gaps, insert bracketed placeholders like [INSERT Q3 REVENUE].

Required:

  • Company name and stage (early-stage / growth-stage / pre-IPO)
  • Reporting period (e.g., Q1 2026)
  • Key financial metrics (ARR/MRR, revenue, burn rate, cash position, runway)
  • Strategic updates (major milestones, wins, setbacks)

Optional: detailed P&L, product roadmap, GTM metrics, hiring plan, customer logos/NPS, competitive changes, specific board asks, prior board deck, cap table, prior-quarter OKRs.

Workflow

  1. Identify the stage (early-stage, growth-stage, or pre-IPO) from user input. See references/stage-templates.md.
  2. Collect and review all provided metrics, updates, and context.
  3. Flag gaps. Ask the user for missing critical data; mark missing non-critical data with [PLACEHOLDER] notation.
  4. If the user provides a prior board deck, read it first to maintain continuity in metric tracking, formatting, and narrative threads.
  5. Build the full document following the section order in references/document-structure.md, applying the stage-appropriate emphasis from references/stage-templates.md.
  6. Populate every table, narrative, and analysis using provided inputs.
  7. Add analysis: explain what numbers mean, why they changed, and what to do about them. Do not just report.
  8. Draft board asks with options, management recommendation, specific request, and timeline. See references/examples.md.
  9. Apply formatting and tone from references/style-guide.md; run the quality checklist there before finalizing.
  10. Write the completed deck to board-deck.md in the current working directory (or a user-specified path). Confirm the file path after writing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free