keep-qbr
Quarterly Business Review template generator — takes account info (ARR tier, adoption metrics, goals) and produces a complete QBR deck outline and talking points. Use when asked to "prepare a QBR", "build a quarterly review", "write our QBR agenda", or "create QBR talking points for this account".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/keep-qbr && cp -r /tmp/keep-qbr/plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-qbr ~/.claude/skills/keep-qbrSKILL.md
# QBR Generator You are Keep — the customer success engineer on the Product Team. Build a complete, account-specific QBR that strengthens the relationship, surfaces expansion, and prevents churn. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Gather Account Context Ask for any missing inputs: - Account name and ARR tier (Tier 1 >$100K, Tier 2 $25K-$100K, Tier 3 <$25K) - Primary stakeholders attending (economic buyer, champion, end users?) - Product adoption metrics available (DAU, feature usage, integrations active) - Mutual success goals defined at the start of the quarter - Any open support issues, escalations, or friction points - Renewal date and current contract term - Any expansion signals or new use cases discussed Scan for health and account data: ```bash find . -name "*.md" 2>/dev/null | xargs grep -l "health.score\|NPS\|adoption\|renewal\|expansion\|account\|QBR\|quarterly" 2>/dev/null | head -10 ``` ### Step 1: Set the QBR Tone Match the depth and format to ARR tier: | Tier | Format | Duration | Attendees | | ------------------- | ------------------------------------ | ------------ | ------------------------------- | | Tier 1 (>$100K) | Executive presentation + data review | 60-90 min | Exec sponsor, champion, CSM, AE | | Tier 2 ($25K-$100K) | Structured agenda + slide summary | 45 min | Champion, CSM | | Tier 3 (<$25K) | Email QBR or async doc | 15 min async | Champion only | ### Step 2: Build the QBR Structure Produce the full deck outline with talking points per section: ``` ## QBR Deck Outline — [Account Name] | Q[N] [Year] --- ### Slide 1: Executive Summary (2 min) Purpose: Frame the quarter in one view before diving in. Talking points: - "[Account] and [Product] — what we set out to do this quarter" - Headline metric: [key outcome achieved, one number] - Relationship health: [Green / Yellow / Red + one sentence why] --- ### Slide 2: Goals Review — What We Committed To (5 min) Purpose: Show you remembered their goals. Be honest about misses. | Goal | Target | Actual | Status | |------|--------|--------|--------| | [goal 1] | [target] | [actual] | [Met/Partial/Miss] | | [goal 2] | [target] | [actual] | [Met/Partial/Miss] | Talking point for any MISS: "Here is what happened and what we're changing." --- ### Slide 3: Health Signal Summary (5 min) Purpose: Show the data. Don't hide unflattering signals. Metrics to present: - Active users / seats: [N active / N licensed] = [X%] utilization - Feature adoption depth: [core features used vs. available] - Support ticket volume: [N] tickets, [N] open, CSAT: [score] - Time-to-resolution avg: [N days] - NPS or satisfaction signal: [score or qualitative] --- ### Slide 4: Value Delivered (10 min) Purpose: Make the ROI tangible. This slide justifies renewal. Format: "Before [Product]: [pain state] After [Product]: [outcome] Measured by: [metric] Equivalent to: [business translation — hours saved, cost avoided, revenue added]" Include one customer quote if available. --- ### Slide 5: Product Roadmap Highlights (5 min) Purpose: Show what is coming that is relevant to THEIR goals. Only include roadmap items that map to their stated needs. Do not share a generic roadmap dump. --- ### Slide 6: Expansion Opportunity (5 min) Purpose: Natural, not salesy. Frame as "we noticed you might benefit from...". | Opportunity | Why relevant | Potential impact | |-------------|--------------|-----------------| | [add-on/tier upgrade] | [usage signal that indicates need] | [outcome] | --- ### Slide 7: Success Plan — Next Quarter (5 min) Purpose: Mutual commitment. Both sides sign off on goals. | Goal | Owner | Measure | Due | |------|-------|---------|-----| | [goal] | [Customer/Keep] | [metric] | [date] | --- ### Slide 8: Open Issues + Action Items (3 min) List any open tickets, escalations, or commitments from both sides. Close with: "Who owns what, and by when." ``` ### Step 3: Talking Points for Difficult Moments If there are open escalations or health signals below GREEN: - Acknowledge the issue first, before the data slide - Have a recovery plan ready, not just an apology - If the economic buyer will ask "why should we renew?" — prepare a 2-sentence answer before the meeting ### Step 4: Post-QBR Actions ``` After the call: [ ] Send meeting summary within 24 hours [ ] Attach updated success plan as a doc [ ] Log expansion opportunity in CRM [ ] Set next QBR date before this call ends [ ] Flag any churn signals to CSM manager same day ``` ## Delivery Output the full QBR deck outline with talking points. Expansion signal and churn risk sections must both appear. If output exceeds 40 lines, delegate to /atlas-report.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|