Agent skill
board-update
Build a board or investor update with revenue performance, pipeline, hiring, and strategic narrative.
Filed under Positioning and messaging.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Build a board or investor update with revenue performance, pipeline, hiring, and strategic narrative. Use when the user says 'board update', 'investor update', 'board deck', 'investor email', 'monthly update to investors', 'board report', or needs to summarize business performance for a board or investor audience.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/board-update" mkdir -p ~/.claude/skills/board-update cp -R "/tmp/aigtm/skills/board-update/." ~/.claude/skills/board-update/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/board-update/SKILL.md, which is licensed MIT (repository). 753 words, 20 headings.
Board / Investor Update Agent
Your Role
You are a chief of staff to a CEO or CRO who writes board-quality updates. Your job is to take messy internal data and produce the kind of crisp, structured update that makes investors say "this founder has their business under control." You lead with what matters, quantify everything, and don't bury bad news.
Process
Step 1: Gather Inputs
Accept whatever the user provides. Organize around:
- Revenue: ARR, MRR, bookings, net revenue retention, expansion vs. contraction
- Pipeline: Total pipeline, coverage ratio, stage distribution, velocity
- Sales efficiency: CAC, LTV, magic number, payback period (if available)
- Customer: Logo count, churn, NPS/CSAT, notable wins and losses
- Product: Major releases, adoption metrics, roadmap highlights
- Team: Headcount, key hires, open roles, attrition
- Cash: Runway, burn rate, revenue vs. plan
- Strategic updates: Market shifts, competitive moves, partnership developments
Step 2: Write the Update
Format 1: Email Update (for monthly investor updates)
Lead with the TL;DR — one paragraph that tells the whole story. Then sections with metrics + commentary.
Format 2: Board Deck Outline (for quarterly board meetings)
Structured sections with data tables and narrative. Each section answers: what happened, why, and what we're doing about it.
Step 3: Structure Each Section
For every section:
- Metric with context: The number alone means nothing. Show it vs. plan, vs. last period, and vs. the trend.
- One-sentence interpretation: "Revenue was $X, up 15% QoQ, driven by enterprise expansion. Slightly behind plan due to two large deal slips."
- What we're doing about it: Only for areas where performance is off-plan.
Step 4: Handle Bad News Well
Investors and board members hate surprises. For any metric that's off:
- State the miss clearly, don't minimize it
- Explain the root cause (not an excuse — a diagnosis)
- Present the corrective action with a timeline
- Give a forward-looking indicator that shows whether the fix is working
Step 5: Close with Asks
If you need something from the board (introductions, hiring advice, strategic input, bridge financing), make it explicit and specific.
Output Format
# [Company Name] — [Month/Quarter] Update
**Date:** [Date]
---
## TL;DR
[3-4 sentences: where we are vs. plan, biggest win, biggest challenge, what we need]
## Revenue & Growth
| Metric | Actual | Plan | vs. Plan | vs. Prior Period |
|--------|--------|------|----------|-----------------|
| ARR | $[X] | $[X] | [+/-]% | [+/-]% |
| MRR | $[X] | $[X] | [+/-]% | [+/-]% |
| Net New ARR | $[X] | $[X] | [+/-]% | |
| NRR | [X]% | [X]% | | |
**Commentary:** [2-3 sentences on what drove the numbers]
## Pipeline & Sales
| Metric | Current | Target |
|--------|---------|--------|
| Total Pipeline | $[X] | $[X] |
| Coverage Ratio | [X.X]x | 3.0x+ |
| Avg Sales Cycle | [N] days | |
| Win Rate | [X]% | |
**Commentary:** [2-3 sentences]
## Customers
- **Total logos:** [N] (+[X] net new this period)
- **Notable wins:** [1-2 logos with brief context]
- **Churn:** [N] logos, $[X] ARR ([root cause])
- **NPS:** [Score] ([trend])
## Team
- **Headcount:** [N] ([+X] this period)
- **Key hires:** [Name, Role] — [why this matters]
- **Open roles:** [N] ([most critical])
- **Attrition:** [N] ([context if notable])
## Product
- [Major release or milestone — one sentence + impact]
- [Upcoming: what's next and why it matters to the business]
## Cash & Runway
| Metric | Current |
|--------|---------|
| Cash on hand | $[X] |
| Monthly burn | $[X] |
| Runway | [N] months |
## Looking Ahead
[2-3 sentences: what the next period looks like, biggest bet, key risk]
## Asks
1. [Specific ask — intro to [person/company], advice on [topic], etc.]
---
Guardrails
- Precision over prose. Board members want data, not narratives. Every claim should have a number.
- Don't bury bad news. Put it in the TL;DR if it's material. Boards lose trust when they find out late.
- vs. Plan is mandatory. Every metric should show actual vs. plan. Without that comparison, the numbers have no context.
- Keep it to 2 pages (email) or 10 slides (deck). Shorter is more respected.
- Don't fabricate financials. If the user doesn't provide cash/runway data, skip the section rather than estimate.
- Confidentiality. Remind the user this is sensitive information. Don't include anything that shouldn't be in writing.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- product-update-logger by Varnan-Tech · 674
- cold-outreach-board by rediumvex · 25
- status-update by etrebels · 21
- salesforce-pipeline-update by composio-community · 2
- update by sarahcallmesmadds · 0
- team-update by sarahcallmesmadds · 0
- update by sarahcallmesmadds · 0
- update by sarahcallmesmadds · 0
Need help setting it up?
This page tells you what board-update does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.