cowork-qbr-builder — Claude Code skill: what it does, how to install
cowork-qbr-builder — a skill for Claude Code that builds a quarterly business review directly from client documents, emails, and tickets. Extracts verified wins and surfaces project risks.
MIT 105 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cowork-qbr-builder -a claude-codeWhat cowork-qbr-builder does
The skill reconstructs the quarter by scanning a folder with client artifacts, including status reports, analytics exports, meeting notes, and email threads. It builds an exact timeline of deliverables, scope updates, and resolved incidents, mapping each item against the initial project objectives.
Every recorded win requires a citation from the source files, cutting unsupported assertions. Misses are documented alongside the remediation steps already underway. The skill gauges account health across support sentiment and meeting attendance, then outputs a structured deck-ready document named qbr-[client]-[quarter].md.
Internal cost figures, margin details, and internal performance notes are filtered out of the final output. If the provided directory has fewer than five substantive artifacts, it flags the documentation gap instead of fabricating narrative filler.
What it helps with
- assemble a structured QBR from raw client correspondence and deliverables
- extract verified client wins tied to concrete metrics and quote citations
- identify account drift and renewal risks ahead of the executive presentation
- draft defensible expansion proposals based on observed customer needs
Example prompts for the agent
- Build the QBR from client-artifacts/acme-q3
- Just the wins from client-artifacts/acme-q3
- Run a health check on the client folder client-artifacts/acme-q3
How to install cowork-qbr-builder
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-qbr-builder -a claude-code2Manually: put the files in place
~/.claude/skills/cowork-qbr-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cowork-qbr-builder/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-qbr-builder -a codex2Manually: put the files in place
.agents/skills/cowork-qbr-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-qbr-builder -a cursor2Manually: put the files in place
.cursor/skills/cowork-qbr-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cowork-qbr-builder2Manually: put the files in place
.github/skills/cowork-qbr-builder/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-qbr-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cowork-qbr-builderManually: put the files in place
.devin/skills/cowork-qbr-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-qbr-builder -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cowork-qbr-builder
How to install cowork-qbr-builder in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cowork-qbr-builder -a claude-code. You can also place the skill file directly at ~/.claude/skills/cowork-qbr-builder/SKILL.md.
What does cowork-qbr-builder do?
It reviews quarterly client artifacts, grades performance against agreed objectives, documents both wins and shortcomings, and drafts a markdown QBR ready for slide conversion.
What inputs does the skill require?
A folder containing the quarter's materials: status reports, usage data, support tickets, meeting notes, and emails, along with documented goals if available.
Source text
SKILL.md · MIT
---
name: cowork-qbr-builder
description: Build a quarterly business review from a client folder -- reports, usage exports, support tickets, meeting notes, emails. Extracts delivered value with receipts, surfaces risks before the client does, and drafts the QBR narrative plus expansion asks. For agencies, consultancies, and CS teams.
tools: Read, Glob, Grep, Write, Bash
model: inherit
---
# 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
1. **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.
2. **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.
3. **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.
4. **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.
5. **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.
6. **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
© OneWave-AI · MIT · OneWave-AI/claude-skills