Systems Lab

Agent skill

qbr-deck-builder

Pull customer usage highlights, support history, feature adoption, NPS/CSAT data, and ROI metrics into a structured QBR deck outline with slide-by-slide content.

dormantSelf-containedActs undeclared1,464 words

Filed under Onboarding, retention and expansion.

From edupegoretti/fluidz-skills · 116 skills · 0 · pushed 2026-03-11

What it does when it runs

Pull customer usage highlights, support history, feature adoption, NPS/CSAT data, and ROI metrics into a structured QBR deck outline with slide-by-slide content. Outputs markdown slide content ready for HTML slides or Google Slides. Designed for CS teams at seed/Series A who run QBRs but don't have time to build decks from scratch.

Read from the skill and the 1 file 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-tools in the frontmatter. It does act, so it runs under whatever permissions your session already grants.
Actions present in the files
writes files

Ask about qbr-deck-builder

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/edupegoretti/fluidz-skills.git /tmp/fluidz-skills
git -C /tmp/fluidz-skills sparse-checkout set "skills/composites/qbr-deck-builder"
mkdir -p ~/.claude/skills/qbr-deck-builder
cp -R "/tmp/fluidz-skills/skills/composites/qbr-deck-builder/." ~/.claude/skills/qbr-deck-builder/

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.

Reproduced in full from edupegoretti/fluidz-skills/blob/a2cf697e2e8ec2ea517d85496e2d5c7f5dc44cd3/skills/composites/qbr-deck-builder/SKILL.md, which is licensed MIT (repository). 1,464 words, 29 headings.

QBR Deck Builder

Turn scattered customer data into a structured QBR deck in minutes. Pulls from whatever data you have — usage stats, support tickets, NPS scores, milestones — and produces slide-by-slide content with talk track notes.

Built for: Founders or CSMs who run quarterly business reviews but spend 3+ hours assembling each deck. The goal is data in, deck out, in one session.

When to Use

  • "Build a QBR deck for [customer]"
  • "I have a business review with [customer] next week"
  • "Prep my quarterly review for [account]"
  • "Generate QBR content for [customer]"

Phase 0: Intake

Account Context

  1. Customer name — Who is this for?
  2. Primary contact — Name, title of the person you're presenting to
  3. Contract details — Plan, MRR/ARR, contract start, renewal date
  4. Review period — What quarter/timeframe are you reviewing? (e.g., Q1 2026)
  5. QBR goals — What outcome do you want? (Renewal confidence, expansion, executive alignment, feature adoption)

Data Inputs (provide what you have)

  1. Usage data — Key metrics for the review period (logins, feature usage, API calls, active users, etc.)
  2. Support history — Tickets opened, resolved, avg resolution time, any escalations
  3. NPS/CSAT — Scores + verbatim comments from this customer
  4. Milestones achieved — Features launched, integrations completed, goals hit
  5. ROI data — Any measurable outcomes: time saved, revenue impacted, efficiency gains
  6. Customer goals — What did they say they wanted to achieve? (From onboarding or last QBR)
  7. Open issues — Anything unresolved, feature requests, known gaps
  8. Expansion opportunity — New use cases, additional teams, upsell potential

Preferences

  1. Deck length — Quick (8-10 slides) or comprehensive (15-20 slides)?
  2. Tone — Executive summary (high-level) or operational deep-dive (detailed)?

Phase 1: Data Synthesis

Before building slides, organize the raw data into QBR themes:

Achievement Summary

  • Goals set vs goals achieved (from onboarding/last QBR)
  • Key wins and milestones this quarter
  • Metrics that improved

Usage & Adoption

  • Feature adoption trends (what they use, what they don't)
  • User growth/engagement within their account
  • Comparison to prior quarter

Support & Reliability

  • Ticket volume and trends
  • Resolution times
  • Any outages or escalations and their resolution

Value & ROI

  • Quantified impact where possible
  • Before/after comparisons
  • Time or cost savings

Looking Forward

  • Upcoming features relevant to them
  • Expansion opportunities
  • Goals for next quarter

Phase 2: Generate Deck Content

Slide 1: Title Slide

[Your Company Logo]

Quarterly Business Review
[Customer Name]

[Quarter] [Year]
Prepared for: [Contact Name], [Title]
Presented by: [Your Name], [Title]
[Date]

Slide 2: Agenda

Today's Agenda

1. Partnership Summary
2. Key Wins This Quarter
3. Usage & Adoption Highlights
4. ROI & Value Delivered
5. Support & Reliability
6. Product Roadmap Preview
7. Goals for Next Quarter
8. Open Discussion

[Estimated time: 30-45 minutes]

Slide 3: Partnership Summary

Partnership at a Glance

| | Detail |
|---|---|
| Customer since | [Date] |
| Current plan | [Plan name] |
| Users/seats | [N] |
| Primary use case | [What they use you for] |
| Account health | [Green/Yellow/Red] |

Key relationship milestones:
- [Month]: [Milestone — e.g., "Onboarding completed"]
- [Month]: [Milestone — e.g., "Expanded to marketing team"]
- [Month]: [Milestone — e.g., "Hit 1,000 [units] processed"]

Talk track: "Before we dive into the numbers, let's ground ourselves on where we are in the partnership..."

Slide 4: Key Wins This Quarter

🏆 Key Wins — [Quarter]

1. [Win 1 — specific achievement with metric]
   → Impact: [What this meant for their business]

2. [Win 2]
   → Impact: [Business impact]

3. [Win 3]
   → Impact: [Business impact]

Customer voice:
"[Direct quote from NPS/Slack/email about a positive experience]"
— [Name], [Title]

Talk track: "Let's start with what went well. These are the highlights I'm most proud of from our work together..."

Slide 5: Usage & Adoption

Usage & Adoption — [Quarter]

[Primary metric]: [Value] ([+/- X%] vs last quarter)
[Secondary metric]: [Value] ([+/- X%])
[Tertiary metric]: [Value] ([+/- X%])

Feature Adoption:
✅ [Feature 1] — actively using
✅ [Feature 2] — actively using
⚡ [Feature 3] — adopted this quarter (new!)
⬜ [Feature 4] — not yet adopted (opportunity)
⬜ [Feature 5] — not yet adopted

Top users: [Names/teams most active]

Talk track: "Here's how your team has been using the product. The standout is [highlight]..."

Slide 6: ROI & Value Delivered

Value Delivered — [Quarter]

Before [Product]:          With [Product]:
─────────────             ─────────────
[Old metric]       →      [New metric]
[Old process]      →      [New process]
[Old cost/time]    →      [New cost/time]

Estimated impact this quarter:
- [X hours saved] across [N team members]
- [X% improvement] in [metric]
- [$X value] in [efficiency/revenue/cost reduction]

Cumulative ROI since partnership:
[$X total value delivered] on [$Y investment] = [Z]x ROI

Talk track: "This is the slide I'm most excited about. Let's talk about the value you've gotten..."

Slide 7: Support & Reliability

Support Summary — [Quarter]

| Metric | [Quarter] | Prior Quarter | Trend |
|--------|-----------|---------------|-------|
| Tickets opened | [N] | [N] | [↑↓→] |
| Avg resolution time | [X hrs] | [X hrs] | [↑↓→] |
| First response time | [X hrs] | [X hrs] | [↑↓→] |
| Escalations | [N] | [N] | [↑↓→] |
| CSAT | [X/5] | [X/5] | [↑↓→] |

[If escalations occurred]:
Notable issues resolved:
- [Issue]: [Resolution + what we did to prevent recurrence]

Platform uptime: [X%]

Talk track: "On the support side, here's how we did. [Highlight improvement or acknowledge issue]..."

Slide 8: NPS/Satisfaction

Customer Satisfaction

NPS Score: [X] ([Promoter/Passive/Detractor])
[If multiple respondents: breakdown chart]

What your team said:
✅ "[Positive quote]" — [Name]
✅ "[Positive quote]" — [Name]
🔧 "[Constructive feedback]" — [Name]

Our response to feedback:
- "[Feedback point]" → [What we did/are doing about it]

Slide 9: Product Roadmap Preview

What's Coming — [Next Quarter]

Relevant to [Customer]:

🚀 [Feature 1] — [1-line description]
   Expected: [Month] | Impact for you: [Why they should care]

🚀 [Feature 2] — [1-line description]
   Expected: [Month] | Impact for you: [Why they should care]

📋 [Feature 3] — [1-line description]
   Expected: [Month]

Your feature requests in progress:
- [Request 1] — Status: [In development / Planned / Under review]
- [Request 2] — Status: [...]

Talk track: "Here's what's coming that I think you'll be excited about..."

Slide 10: Goals for Next Quarter

Proposed Goals — [Next Quarter]

| Goal | Metric | Target | Owner |
|------|--------|--------|-------|
| [Goal 1] | [How we measure] | [Target number] | [Who drives] |
| [Goal 2] | [Metric] | [Target] | [Owner] |
| [Goal 3] | [Metric] | [Target] | [Owner] |

Adoption targets:
- Get [team/department] onboarded to [feature]
- Increase [metric] from [current] to [target]

Training/enablement:
- [Planned session or resource]

Talk track: "Based on where you are and where you want to go, here are the goals I'd suggest for next quarter..."

Slide 11: Expansion Opportunity (if applicable)

Growth Opportunity

Current: [What they have today]
Opportunity: [What they could add]

Why now:
- [Reason 1 — tied to their business context]
- [Reason 2 — tied to product capability]
- [Reason 3 — tied to ROI already demonstrated]

Proposed next step:
[Specific ask — e.g., "Pilot with marketing team for 30 days"]

Investment: [Additional cost]
Expected additional value: [ROI projection]

Talk track: "Given the results we've seen, there's a natural next step that I think would multiply the value..."

Slide 12: Open Discussion & Next Steps

Discussion & Next Steps

Questions for you:
1. [Strategic question about their priorities]
2. [Question about upcoming changes that might affect usage]
3. [Question about satisfaction/concerns]

Agreed next steps:
☐ [Action 1] — Owner: [Name] — By: [Date]
☐ [Action 2] — Owner: [Name] — By: [Date]
☐ [Action 3] — Owner: [Name] — By: [Date]

Next QBR: [Proposed date]

Phase 3: Output

Save all content to clients/<client-name>/customer-success/qbr/[customer-slug]-[quarter]-[YYYY].md.

Optionally chain to create-html-slides to produce a presentable HTML deck.

Cost

ComponentCost
All deck generationFree (LLM reasoning)
HTML slides (if chained)Free
TotalFree

Tools Required

  • None. Pure reasoning skill — takes data inputs and produces structured slide content.
  • Optional: create-html-slides for HTML presentation output
  • Optional: visual-brand-extractor for branded deck styling

Trigger Phrases

  • "Build a QBR deck for [customer]"
  • "Prep my quarterly review for [account]"
  • "Generate QBR content for [customer]"
  • "Run the QBR deck builder"

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.

Need help setting it up?

This page tells you what qbr-deck-builder 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.