Install
$ agentstack add skill-etrebels-claude-code-growth-os-qbr-prep ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 in [docs/operating-model.md](../../../docs/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-playworks 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-play.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: etrebels
- Source: etrebels/claude-code-growth-os
- License: MIT
- Homepage: https://www.langoptima.com/features/growth
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.