acquire-codebase-knowl…
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document…
Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the
$ npx -y skills add github/awesome-copilot --skill gtm-board-and-investor-communication --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/gtm-board-and-investor-communicationContext preview
The summary Claude sees to decide when to auto-load this skill.
Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the
name: gtm-board-and-investor-communication description: Board meeting preparation, investor updates, and executive communication. Use when preparing board decks, writing investor updates, handling bad news with the board, structuring QBRs, or building board-level metric discipline. Includes the "Three Things" narrative model, the 4-tier metric hierarchy, and the pre-brief pattern that prevents board surprises. license: MIT metadata: author: Smit Patel (https://linkedin.com/in/smitkpatel) source: https://github.com/beingsmit/technical-product-gtm
Structure board meetings, investor updates, and executive communication that builds trust and drives decisions — not slide decks that nobody reads.
**Triggers:**
**Context:**
---
**The Pattern:**
Most board meetings start with a data dump. Slide after slide of metrics, then 10 minutes of Q&A where board members try to figure out what it all means.
Flip it. The narrative should lead; data should confirm.
**How It Works:**
Open with where you are in the journey. Not "here's our ARR" but "here's what we believed coming into the quarter, what we learned, and where that puts us now." Then show the data that validates the narrative.
**Board Meeting Structure:**
**Pre-Read (Sent 48-72 Hours Before)**
**The Meeting (90-120 Minutes)**
1. **Market context and questions on pre-read** (15 min)
2. **CEO strategic update — The "Three Things"** (15 min)
3. **Decision items** (30-45 min)
4. **Deep dive** (20-30 min)
5. **Closing** (10 min)
**Common Mistakes:**
---
**The Pattern:**
Businesses are too complex to summarize in one headline. Three distinct points — what's working, what's not, what's changing — let the board grasp status and trajectory in minutes.
**What's Working (2-3 areas):** Be specific. Not "sales are going well" but "closed first six-figure enterprise deal, validating the commercial motion." Quantify momentum:
**What's Not Working (1-2 areas):** Be equally specific. Not "we had some challenges" but "self-serve conversion is weak — strong awareness but 0.1% conversion rate." Board needs to understand the actual problem, not a euphemism.
**What We're Doing About It (for each "not working"):** Articulate specific changes. What product changes? What org changes? What's the timeline? What resources are committed?
**Why This Works:**
Board members read dozens of updates. The Three Things model gives them a mental filing system: momentum (feel good), risk (pay attention), agency (this team handles problems). Without it, boards either over-index on one bad metric or miss the real issue buried in a 40-slide deck.
---
**The Pattern:**
It doesn't matter if you hit 100K users if you were aiming for 50K — or if you missed 200K. Context is everything. Show progress toward your goal, not just the number.
**How to Frame Progress:**
**The Rules:** 1. Set the goal upfront (every metric needs a target) 2. Show progress as % toward goal, not just absolute number 3. Acknowledge misses; explain pivots 4. State confidence level based on trajectory
**Common Mistake:**
Changing goals when you miss them. Boards track this. If Q1 target was 100K and you hit 60K, don't make Q2 target 75K and call it "revised guidance." State the miss, explain why, show the recovery plan. Credibility comp
A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.
Repo: github/awesome-copilot
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document…
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc…
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS…
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting…
Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns",…
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.