Agent skill
qbr-prep
Turn a customer's recent calls, adoption signal, and roadmap status into a QBR brief that leads with the outcome they bought.
Filed under Onboarding, retention and expansion.
From etrebels/claude-code-growth-os · 20 skill entries · 21 · pushed 2026-10-03
What it does when it runs
Turn a customer's recent calls, adoption signal, and roadmap status into a QBR brief that leads with the outcome they bought. Trigger when a quarterly business review is coming up, before a renewal or value-review call, or when the user says "QBR prep", "build the QBR", "quarterly review for X", or "value review".
Automated analysis of the skill and the 0 files 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-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/etrebels/claude-code-growth-os.git /tmp/claude-code-growth-os git -C /tmp/claude-code-growth-os sparse-checkout set ".claude/skills/qbr-prep" mkdir -p ~/.claude/skills/qbr-prep cp -R "/tmp/claude-code-growth-os/.claude/skills/qbr-prep/." ~/.claude/skills/qbr-prep/
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.
The skill
Source on GitHub ↗Reproduced in full from etrebels/claude-code-growth-os/blob/3e0c2d7d1fc545d35073011208d8da3f845183fb/.claude/skills/qbr-prep/SKILL.md, which is licensed MIT (repository). 337 words, 2 headings.
QBR Prep
The recurring right-side ritual. A QBR isn't a status meeting or a feature tour — it's a value-realization review: did the customer get the outcome they bought, and what's the next one? This assembles the brief from what's already in the repo, so the review leads with their metric, not your release notes.
From the account in ops/customers.md, its recent meeting notes (in ops/ or demo/meetings/), and ops/roadmap-signals.md:
- Outcome recap — lead here. State the value hypothesis the deal was bought on, then the evidence it's landing: the adoption signal, what's live, who's using it. Their metric, their words. This is the spine of the brief; everything else hangs off it.
- Risks, named first. What isn't landing yet — a stalled workflow, a quiet stretch, a single-threaded relationship — said before the customer raises it. Naming the gap yourself is what makes the recap credible.
- What shipped for them. Pull anything in
ops/roadmap-signals.mdtied to this account that's now Shipped, with its buyer-facing line. "You asked, we shipped" closes the loop the customer started (handoff H5 indocs/operating-model.md) and earns the next ask. - The next desired outcome. Frame the expansion thesis as their next goal — the adjacent team or use case — not a quota. If it's real, this is the seed
expansion-signalworks after the QBR. - One ask, one offer. A single ask (a reference, a case study, an intro) and a single offer (an expansion, a new team, a deeper rollout). More than one of each dilutes both.
Output a brief you can walk in with. Don't invent outcomes the notes don't support — a QBR that claims value the customer didn't feel is the fastest way to lose the renewal.
Depth
- quick: the one-page brief — outcome recap, top risk, the one ask.
- standard: the full brief above, ready to present from.
- deep: + a slide-ready outline to hand to a deck tool, and the expansion thesis written up for
expansion-signal.
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.
- sales-prep by zubair-trabzada · 1,422
- meeting-prep-cc by BrianRWagner · 443
- meeting-prep by explorium-ai · 200
- event-host-prep-dossiers by getaero-io · 66
- meeting-prep-brief by JJenglert1 · 58
- meeting-prep-brief by Othmane-Khadri · 58
- qbr-ebr-builder by NEON-Rutger · 51
- event-prep by markster · 51
Need help setting it up?
This page tells you what qbr-prep 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.