Cowork Qbr Builder Skill for Claude

Cowork QBR Builder

Prepare a QBR the way a top customer-success lead does: prove the value delivered with specifics, name the problems before the client names them, and earn the expansion conversation. Input: a folder of client artifacts for the quarter -- status reports, deliverables, usage/analytics exports, support tickets, meeting notes, email threads -- plus the engagement's stated goals if documented.

Workflow

• Reconstruct the quarter. From the folder, build a timeline of what actually happened: deliverables shipped (with dates), meetings held, issues raised and resolved, scope changes. Distinguish documented fact from inference.
• Score against goals. Map the quarter's work to the engagement's stated objectives. For each goal: status (achieved/on-track/at-risk/missed), the evidence, and the metric where one exists. If no goals were ever documented, say so -- and propose measurable ones for next quarter, because that gap is itself a finding.
• Mine the wins. Extract concrete value receipts: metrics that moved, hours saved, incidents prevented, quotes from the client's own emails ("this saved our launch"). Specific and cited beats impressive and vague.
• Face the misses. List what slipped, stalled, or disappointed -- with the honest reason and the fix already in motion. A QBR that hides the miss the client remembers loses the room.
• Health and risk read. From ticket sentiment, email response patterns, meeting attendance, and champion activity: engagement health (strong/stable/drifting), risks (champion departure, budget noise, declining usage), and renewal posture.
• Draft the QBR. Output qbr-[client]-[quarter].md structured for a deck: executive summary, goals scorecard, wins with receipts, misses with fixes, next-quarter plan, and -- only where the evidence supports it -- 1-2 expansion recommendations framed around the client's goals, not your revenue. Hand to pptx or presentation-design-enhancer for the deck build.

Rules

• Every win cites its source artifact. Unsupported claims get cut, not softened.
• Report the quarter that happened, not the quarter that was planned. If the folder shows drift, the QBR shows drift.
• Client's language over your jargon: pull their vocabulary from their own emails and notes.
• Expansion asks must trace to an observed need in the artifacts. No need observed, no ask drafted.
• Keep confidential internal material out: internal cost notes, margin discussions, and team-performance comments in the folder never surface in client-facing output.
• If the folder is thin (< 5 substantive artifacts), lead with the documentation gap and build what is defensible rather than padding.

Quick Commands

• "Build the QBR from [folder]" -- full workflow
• "Just the wins" -- step 3, receipts list
• "Health check" -- step 5 only
• "What should next quarter's goals be?" -- proposed measurable objectives from the evidence