plugins/pm-cs/skills/qbr-deck/SKILL.md
Build a Quarterly Business Review (QBR) deck structure and narrative for a customer account. Use when asked to prepare a QBR, business review meeting, executive review, or quarterly check-in with a customer. Produces a slide-by-slide QBR structure with talking points, metrics review, value narrative, and mutual next steps.
npx skillsauth add mohitagw15856/pm-claude-skills qbr-deckInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Produce a complete Quarterly Business Review deck — structured, data-backed, and customer-focused. A good QBR demonstrates value delivered, aligns on goals for the next quarter, and strengthens the executive relationship. It should never feel like a product demo or a vendor update.
Ask for these if not already provided:
[Quarter] [Year] Business Review
Date: [Date] | Location / Call link: [TBC] Customer attendees: [Names and roles] [Your company] attendees: [Names and roles]
| Time | Topic | Owner | |---|---|---| | 0:00 | Welcome and introductions | CSM | | 0:05 | [Last quarter] — how did we do? | CSM + Customer | | 0:20 | Value delivered — business impact | CSM | | 0:35 | What's coming — roadmap preview | CSM / Product | | 0:45 | [Next quarter] — goals and priorities | Customer | | 0:55 | Actions and mutual commitments | CSM | | 1:00 | Close | |
Talking point: "We've kept today to 60 minutes. We want as much of this to be a conversation as possible — please push back, redirect, and ask questions throughout."
Partnership snapshot:
Talking point: "Before we dive in — a quick picture of where we are. [X] months in, [Y] active users, and this is our [Nth] QBR together."
| Goal | Set in [Last QBR / Kickoff] | Status | |---|---|---| | [Goal 1] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed | | [Goal 2] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed | | [Goal 3] | [What we committed to] | ✅ Achieved / ⚠️ Partial / ❌ Missed |
For any partial or missed goal: state what happened and what changes next quarter.
Talking point: "Let's start with accountability. Here's what we said we'd achieve last quarter — let's be honest about where we landed."
Quarter-over-quarter trend:
| Metric | [Q-1] | [Q] | Change | |---|---|---|---| | Monthly active users | [N] | [N] | +/-X% | | Sessions per user per week | [N] | [N] | +/-X% | | [Key feature 1] adoption | [X]% | [X]% | +/-X% | | [Key feature 2] adoption | [X]% | [X]% | +/-X% |
Highlights:
Opportunity:
Talking point: "Usage is [up / stable / something we want to talk about]. The area I'd like to focus on is [feature] — we're not seeing the adoption we'd expect given [their goal], and I want to understand why."
Lead with outcomes, not activity.
[Outcome 1: customer's primary success metric]
[Outcome 2]
[Outcome 3]
Customer evidence (use if available):
"[Quote from champion or user about value experienced]"
Talking point: "This is the section I most want your input on. Are these the outcomes that matter to your business? Are there other ways you're measuring success that we should be tracking?"
| Metric | This quarter | Last quarter | Trend | |---|---|---|---| | Tickets raised | [N] | [N] | ↑ / → / ↓ | | Average resolution time | [X hrs] | [X hrs] | ↑ / → / ↓ | | P1 / critical issues | [N] | [N] | ↑ / → / ↓ | | CSAT score | [X/10] | [X/10] | ↑ / → / ↓ |
Notable issues this quarter:
What we're doing differently:
Focus only on what's relevant to this customer's goals. Do not dump the full roadmap.
| Feature / Improvement | Expected | Why it matters to [Account Name] | |---|---|---| | [Feature 1] | [Q+1] | [Direct link to their goal or pain point] | | [Feature 2] | [Q+1 / Q+2] | [Direct link] | | [Feature 3] | [H2] | [Direct link] |
Talking point: "I've filtered the roadmap to what I think matters most to your team. I'd love your reaction — are these the right priorities from your perspective?"
Customer input section — facilitate, don't present.
Prompt questions:
Capture live:
| Goal for next quarter | Owner (customer) | How we'll support it | How we'll measure it | |---|---|---|---| | [Goal 1] | [Name] | [CSM / product action] | [Metric] | | [Goal 2] | [Name] | [CSM / product action] | [Metric] |
[Your company] commits to:
[Account Name] commits to:
Next touchpoint: [Date of next check-in or mid-quarter review]
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.