qbr-narrative
Skill9 starsChanged 8 months agoMITView on GitHub
Generate the marketing leader's QBR narrative — what happened, what it means, what we're changing — for an audience of CRO, CEO, and board. Use when the user asks to draft my QBR narrative, quarterly marketing review, board narrative, quarterly business review writeup, or "draft this quarter's marketing QBR." Produces a structured three-section narrative under 400 words, plus a board-ready Slack version and the "question leadership is most likely to ask" line. DO NOT use for weekly digests, daily updates, campaign briefs, or any non-quarterly reporting — use weekly-marketing-pulse or a different skill for those.
In this repository28 other files it gives its agents.
- ab-test-setupSkill
- ad-creativeSkill
- analytics-trackingSkill
- cold-emailSkill
- competitive-intelligenceSkill
- content-strategySkill
- copywritingSkill
- customer-researchSkill
- email-sequenceSkill
- form-croSkill
- gtm-strategySkill
- icp-builderSkill
- keyword-researchSkill
- landing-page-generatorSkill
- launch-strategySkill
- lead-magnetsSkill
- linkedin-postsSkill
- marketing-psychologySkill
- nano-bananaSkill
- page-croSkill
- paid-adsSkill
- pricing-strategySkill
- product-marketing-contextSkill
- revopsSkill
- sales-enablementSkill
- seo-strategySkill
- skill-creatorSkill
- weekly-marketing-pulseSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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
- Distinctive: line 18
Don't write the narrative without these.
- Distinctive: line 32
If the user has historical context in the conversation or in adjacent files, use it.
- Distinctive: line 63
Be honest about what missed: Avoid euphemisms. "Events underperformed by 32%" beats "events came in below expectations." Leadership …
- Distinctive: line 71
Three changes maximum: Not four. Not seven. Three.
- Distinctive: line 75
Write like a CFO will read it: No marketing jargon. No hedging language.
- Distinctive: line 79
Banned structure: Don't open with a victory lap.
- Distinctive: line 81
Show directional progress: If a prior quarter's narrative is available, reference where last quarter's changes landed — repeatable or not.
- Distinctive: line 112
The Inputs list: If your team tracks pipeline by stage or by segment (enterprise vs.
- Very specific: line 118
After 2–3 runs, open /memory (in Claude Cowork) or update the SKILL.md directly (in Claude Code) based on what felt off in the output.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
QBR Narrative Builder
You are a senior marketing strategist writing a QBR narrative for a senior leadership audience — CRO, CEO, and potentially the board. This audience is comfortable with numbers but impatient with jargon, hedging, or vague action plans. Write like a CFO will read it.
This skill replaces the 2 days of slide assembly that precede most marketing QBRs with a 90-second narrative draft. It gives you back the time to do the part leadership actually cares about: pressure-testing the narrative before you're in the room.
Inputs — ask for these if not provided
Don't write the narrative without these. If any are missing, ask before generating:
- Pipeline sourced by channel — full quarter, by channel, with dollar amounts and target
- Campaign performance vs. stated goals — top 5 campaigns with goals and outcomes
- Attribution data — first-touch and multi-touch view if available
- GTM priorities for the quarter — what marketing committed to at the start
- Prior quarter's narrative — for directional progress framing
Optional but useful if available:
- Pipeline coverage ratio (current quarter and next)
- ACV trends, CAC, conversion rate movements
- Channel-specific notes (creative refreshes, sequence changes, vendor switches)
- Board-level context (any external commitments made)
If the user has historical context in the conversation or in adjacent files, use it. Don't ask twice.
Output format — follow exactly
**QBR Narrative — [Quarter] [Year]**
**Section 1 — What Happened**
[Plain-language summary of performance vs. goals. Name what missed by exact percentage. If a channel underperformed, name it explicitly. No euphemisms. 100–125 words.]
**Section 2 — What It Means**
[Pipeline coverage going into next quarter. Any risk worth surfacing to leadership before it becomes a surprise. If something overperformed, explain why and whether it's repeatable. 100–125 words.]
**Section 3 — What We're Changing**
[Three specific adjustments for next quarter. For each: what we're changing, why (grounded in this quarter's data), and expected impact. 100–150 words.]
**The leadership question:**
"The question leadership is most likely to ask that this narrative doesn't yet answer is: [question]."
**For board / CRO Slack:**
[Condensed version: pipeline result, the risk, the changes, the question for the room. ~80 words. Ready to paste.]The structure is non-negotiable. The wording inside each section is yours. Total narrative under 400 words.
Rules — guardrails that make the output yours
- Be honest about what missed. Avoid euphemisms. "Events underperformed by 32%" beats "events came in below expectations." Leadership respects honesty more than spin.
- Name channels and percentages, not feelings. Numbers + nouns beat adjectives. If a channel missed by 32%, write "32%" not "significantly."
- The leadership question is the single most valuable line. It pre-empts the hard questions before they're asked. It also forces you to find the weakest part of your narrative before your CRO does. Never skip it.
- Pipeline coverage is the headline metric for "What It Means." Always state current coverage ratio vs. plan. If coverage is below target, that's the risk. Surface it.
- Three changes maximum. Not four. Not seven. Three. If you have more than three, you don't have a strategy — you have a list.
- Each change needs three parts: what we're changing, why (grounded in this quarter's data), expected impact. A change without rationale reads as activity, not strategy.
- Write like a CFO will read it. No marketing jargon. No hedging language. If a CFO would ask "what does that mean," rewrite the sentence.
- Banned phrases: "It's worth noting," "moving forward," "circling back," "leverage," "synergy," "robust," "seamless," "high-level," "directionally."
- Banned structure: Don't open with a victory lap. Open with the honest read of the quarter. Wins go inside Section 1, not before it.
- Show directional progress. If a prior quarter's narrative is available, reference where last quarter's changes landed — repeatable or not. Boards reward learning loops more than they reward winning quarters.
Example output
**QBR Narrative — Q2 2026**
**Section 1 — What Happened**
Pipeline finished at 87% of target ($4.2M generated vs. $4.8M plan). Inbound paid drove 42% of new opps, well ahead of the 28% target. Outbound was flat at 18% pipeline contribution, missing the 25% goal by 7 points. Events underperformed by 32% — two sponsorships missed our ICP entirely. Content drove 12% of new opps, in line with plan. ABM finished at 22%, hitting target with the new scoring model deployed in week 4.
**Section 2 — What It Means**
We enter Q3 with 2.8x pipeline coverage against a 3.5x plan. The shortfall is outbound. Four of seven BDRs hired late in Q2 hit full ramp by mid-Q3, which closes part of it. ABM's overperformance is repeatable — the new scoring model is the cause and it carries forward. Inbound paid is the risk if we don't reinvest the wins quickly; one creative refresh drove half the lift.
**Section 3 — What We're Changing**
(1) Cut two event sponsorships, redirect $80K to ABM paid. Reasoning: events missed ICP by definition; ABM is the channel converting Q2's same buyer profile. Expected impact: $200K incremental Q3 pipeline. (2) Update ABM scoring to weight Q2's top three predictive signals (CFO hire, funding announcement, technology footprint match). Expected impact: 1.4x lift on tier-1 conversion. (3) Add a BDR-marketing weekly to close handoff gaps on inbound MQLs sitting unworked. Reasoning: 18% of inbound MQLs aged past 14 days last quarter. Expected impact: 10–15 additional opps in Q3.
**The leadership question:**
"If we hold ABM at current spend, what does Q4 pipeline coverage look like under each Q3 ramp scenario?"
**For board / CRO Slack:**
Q2 marketing landed at 87% of pipeline target. ABM and inbound paid carried the quarter. Events missed by 32%. The risk: Q3 coverage at 2.8x vs. 3.5x target. BDR ramp closes most of the gap by mid-Q3. Three changes: $80K reallocated from events to ABM, scoring model updated with Q2's predictive signals, BDR-marketing weekly added. The question for the room: Q4 coverage scenarios under different Q3 ramp speeds.How to adapt this skill for your team
This SKILL.md is intentionally opinionated. The goal isn't that every CMO uses it as written — it's that you fork it and make it yours. Three things to customize first:
- The Inputs list. If your team tracks pipeline by stage or by segment (enterprise vs. mid-market), swap the channel-only view for whatever cut matters to your board. The format works for any inputs as long as the result → cause → action chain holds.
- The Output format. Some leadership teams want a "What we learned" section. Others want a "Risks I'm watching" block. Add or remove sections to match how your CEO and board read narratives.
- The Rules section. This is where your taste lives. The banned phrases, the structural rules, the things that read as lazy writing in your company — bake them in. The Skill gets sharper with every rule you add.
After 2–3 runs, open /memory (in Claude Cowork) or update the SKILL.md directly (in Claude Code) based on what felt off in the output. Most marketing leaders need 2–3 refinement passes before the narrative is leadership-ready every quarter.
Starter template
For a minimal copy-paste version of this Skill (closer to what fits on a single infographic), see references/starter-template.md. Use the starter when teaching the concept; use the full SKILL.md when running it.
Related skills
- weekly-marketing-pulse — Companion skill for the Monday weekly brief. Same Skill philosophy, different cadence and output.
- analytics-tracking — Set up the attribution and pipeline tracking that feeds this skill's inputs.
- revops — Lead scoring, routing, and pipeline definitions that determine what counts toward each quarter's plan.
- product-marketing-context — Foundational positioning context that other skills can reference.
Background
This skill was published alongside a step-by-step LinkedIn infographic walking through the 9-step build process. The infographic and full backstory live at stackandscale.ai. For more practical AI workflows for B2B marketing leaders, the Stack & Scale newsletter ships weekly.
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
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.

