Agent skill · Audited from source

Board Deck Builder

skill · borghei/Claude-SkillsNOASSERTION licenceAudited 19 Oct 2026 · source 6e3fcbdbb5cf

★ 949pushed 12 days agoversion 2.0.0
!CAUTIONGrade B · 89/100 · 5 findings · 6e3fcbd
949repo stars · whole borghei/Claude-Skills

Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit 6e3fcbdbb5cf and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 5 findings, 0 critical or high. What it does: 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.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Board Deck Builder (borghei/Claude-Skills)”. Retrieved 19 Oct 2026. https://modelsatlas.com/skills/borghei/board-deck-builder

2 skills are called “Board Deck Builder”. You are viewing borghei/Claude-Skills.

Trust audit

Audit 0.4.1 · source read 19 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high5 medium0 low0 info

CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 13,985 of 14,816 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN5
L1 Static sourceSecrets, path traversal, supply chain, hidden codePASS0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (5)

Audit 0.4.1 · source sha 6e3fcbdbb5cf · 19 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherborghei GitHub userOwner of the repository this skill is read from
  • Source folderborghei/Claude-Skills/c-level-advisor/board-deck-builderThe exact folder we audited
  • LicenceNOASSERTIONAs the repository states it
  • Commit pinned for this verdict6e3fcbdbb5cfA new audit runs when the source changes
  • Repository statusNot archivedLast push 12 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its 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.

---
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
  author: borghei
  category: c-level
  domain: board-governance
  updated: 2026-03-09
  frameworks:
    - deck-structure
    - narrative-framework
    - bad-news-delivery
    - section-templates
    - fundraising-format
  triggers:
    - 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
    - investor report
    - board materials
    - board slides
---
# 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 | Un

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 6e3fcbd

Download folder ↗
git clone https://github.com/borghei/Claude-Skills
git -C Claude-Skills checkout 6e3fcbdbb5cf

The author documents no install command, so this uses the repository directly. Our verdict covers commit 6e3fcbdbb5cf only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. !CAUTION B 89 / 100

    first audit · source 6e3fcbdbb5cf

A11y Audit!CAUTION

borghei/Claude-Skills

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

★ 949Grade B
Agent Designer!CAUTION

borghei/Claude-Skills

Designs multi-agent system architectures with orchestration patterns, tool schemas, and performance evaluation. Use when building AI agent systems, designing agent workflows, creating tool schemas, or evaluating agent…

★ 949Grade B
Agent Protocol!CAUTION

borghei/Claude-Skills

Design AI agent communication protocols: MCP tool schemas, A2A, function calling, and inter- agent messaging. Use when building multi-agent systems, defining tool interfaces, or implementing agent-to-agent communication.

★ 949Grade B
Agent Workflow Designer!CAUTION

borghei/Claude-Skills

Design multi-agent orchestration with workflow DAGs, routing, handoff protocols, and state management. Use when building pipelines of specialized agents, designing fan-out/fan-in patterns, or implementing fault-tolerant…

★ 949Grade B
Agenthub!CAUTION

borghei/Claude-Skills

Multi-agent DAG orchestration for workflows where AI agents collaborate via dependency graphs, covering agent spawning, output merging, and quality evaluation. Use when a task needs multiple specialized agents or to…

★ 949Grade B
Analytics Engineer!CAUTION

borghei/Claude-Skills

Analytics engineering across data modeling, dbt, transformation, and semantic layers. Use when building dbt models, designing star schemas, writing staging or mart SQL, configuring data tests, or optimizing warehouse…

★ 949Grade B

Questions about Board Deck Builder

What does the Board Deck Builder skill do?
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. Installs on Claude Code, Cursor, Codex, Gemini, Copilot, and 6 other AI assistants.
Is Board Deck Builder safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Board Deck Builder access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (6e3fcbdbb5cf), read on 2026-10-19. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.