Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Qbr Deck

ASecurity

Build a structured Quarterly Business Review deck for a customer account. Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck", "renewal prep", "executive check-in", "90-day review", or "customer business review" - even if they don't use the acronym. Applies to CSMs preparing for executive-level customer meetings focused on value delivered, health, and next quarter alignment.

20 stars
0 votes
0 copies
2 views
Added 10/4/2026
ai-agentsrustgo

Works with

cli

Security Analysis

A100/100

Scanned 10/4/2026

$npx -y skills add qa-aman/claude-skills --skill qbr-deck --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Qbr Deck?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Qbr Deck
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/qa-aman-qbr-deck/badge)](https://www.skillsdirectory.com/skills/qa-aman-qbr-deck)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: qbr-deck
description: >
  Build a structured Quarterly Business Review deck for a customer account.
  Use when user says "QBR", "quarterly business review", "prep my QBR", "build the deck",
  "renewal prep", "executive check-in", "90-day review", or "customer business review" -
  even if they don't use the acronym. Applies to CSMs preparing for executive-level customer
  meetings focused on value delivered, health, and next quarter alignment.
---

## Overview

A QBR is a structured executive conversation, not a product demo or status update. Based on
"Customer Success" by Mehta, Steinman & Murphy, the QBR's purpose is to demonstrate realized
value, align on goals, and earn continued investment. The meeting fails when it looks backward
without a forward commitment.

The core insight: every slide must answer "so what?" from the customer's perspective. Data
without context is noise. Health scores without recommended actions are incomplete.

## Workflow

### Step 1: Gather inputs before building anything

Collect the following before touching the deck:

- **Goals from last QBR**: What did [customer name] say they wanted to achieve this quarter?
- **Usage data**: Logins, feature adoption rate, active users vs. licensed seats
- **Health score**: Current score and 90-day trend (improving, stable, declining)
- **Support tickets**: Volume, average resolution time, any unresolved critical issues
- **Outcomes achieved**: Measurable business results tied to your product
- **Renewal timeline**: Months until renewal, ARR at stake
- **Expansion signals**: New use cases, headcount growth, adjacent teams not yet using product

If you don't have all inputs, note explicitly what is estimated vs. confirmed.

### Step 2: Structure the deck in this sequence

**Slide 1 - Partnership Summary**
One-line: "[Your company] x [Customer name] - Q[X] [Year] Review"
Include: CSM name, executive sponsor (customer side), renewal date, ARR.

**Slide 2 - Goals We Agreed On Last Quarter**
List 2-4 goals verbatim from prior QBR or success plan. Use the customer's language, not yours.
Mark each: Achieved / Partially Achieved / Missed.

**Slide 3 - Value Delivered**
Lead with business outcomes, not product features.

| Outcome | Metric | Last Quarter | This Quarter | Change |
|---------|--------|-------------|--------------|--------|
| [business result] | [measure] | [value] | [value] | [delta] |

Example row: "Reduced onboarding time | Hours per new hire | 8h | 3h | -63%"

**Slide 4 - Usage and Adoption Health**

| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| MAU / licensed seats | >80% | [X]% | Green/Yellow/Red |
| Feature adoption (core) | >70% | [X]% | |
| Support ticket volume | <[N]/mo | [X] | |

Include a 90-day trend if available.

**Slide 5 - Health Score Summary**
Show composite health score and breakdown by dimension (usage, engagement, NPS, support,
financial). Flag any dimension scoring Yellow or Red with the specific risk named.

Do not hide Red scores. Customers respect transparency. Hiding problems erodes trust before renewal.

**Slide 6 - Goals for Next 90 Days**
List 2-4 specific, measurable goals for next quarter:

- **Goal**: [specific outcome]
- **Owner**: [customer name / your CSM team]
- **Measure**: [how you will know it is done]
- **Target date**: [month]

**Slide 7 - Open Items and Asks**
Outstanding product requests, blockers, and anything you need from the customer.
Name owner and due date for each item.

**Slide 8 - Roadmap Preview** (optional, only if directly tied to customer goals)
Show 1-2 upcoming features that address goals the customer stated in their own words.
Padding with irrelevant features weakens credibility.

### Step 3: Apply the "so what?" test to every slide

After drafting, ask for each slide: "Why does this matter to [customer name]'s business?"
If you cannot answer in one sentence, rewrite or cut the slide.

### Step 4: Prepare for likely objections

Anticipate the three most common concerns before the meeting:

1. "We're not seeing the ROI we expected" - have outcome data and a remediation plan ready
2. "Adoption is lower than we'd like" - have a specific activation plan, not just acknowledgment
3. "We're evaluating alternatives at renewal" - have a retention offer or executive escalation path

## Anti-Patterns

**1. Activity report masquerading as a QBR**
Bad: "This quarter we ran 4 training sessions, resolved 12 tickets, and shipped 3 updates."
Good: "Onboarding time dropped 60% this quarter. Here's what drove it and what we're targeting next."

**2. Hiding health problems**
Bad: Only showing green metrics. Glossing over low adoption.
Good: "Active users are at 52% of licenses - below our 80% target. Here's the remediation plan."

**3. No forward commitment**
Bad: Deck ends at "here's what happened." No goals, no owners, no dates.
Good: Every QBR closes with 2-4 signed-off goals for next quarter with named owners.

**4. Generic roadmap slides**
Bad: Showing the full product roadmap as a feature list.
Good: Selecting 1-2 items that directly address goals the customer stated in their own words.

**5. Vendor language instead of customer language**
Bad: "We improved platform engagement scores by 14 points."
Good: "Your goal was to reduce rep ramp time. We cut it from 8 weeks to 5."

## Quality Checklist

- [ ] Every metric is tied to a goal stated in a prior QBR or success plan
- [ ] No metric appears without context (target, trend, or "so what")
- [ ] Health score shows dimension breakdown - no composite-only slides
- [ ] Red and Yellow items named explicitly with a remediation plan
- [ ] Next 90-day goals are specific, measurable, and have named owners
- [ ] Customer's own language used for goals and outcomes
- [ ] Deck is 8 slides or fewer - no padding
- [ ] Renewal date and ARR visible on slide 1
- [ ] Open items have owners and due dates
- [ ] No personal names, internal tool names, or company-specific references in template

Attribution

qa-amanqa-aman
View sourceSee grades on GitHubMore from qa-aman →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →