Skip to content
cccskills
FreePublished on GitHub

cowork-qbr-builder

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audit websites for accessibility issues and WCAG compliance. Use when checking accessibility, fixing a11y issues, or ensuring WCAG compliance.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills352Updated Oct 2, 2026

Deploy a 2-layer parallel agent hierarchy for large, parallelizable work — big refactors, multi-file migrations, codebase-wide audits, bulk generation. A top-tier commander (Fable or Opus) orchestrates the swarms; the user picks a power level (Max Power / Heavy / Balanced / Economy) that sets the Opus/Sonnet/Haiku model mix per layer. Layer 1 is 3-50+ specialist agents, each with its own full context window; Layer 2 is 2+ sub-agents per member. Includes git safety, tiered sizing, a pre-deploy gate, phantom-completion checks, and multi-wave follow-up.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills352Updated Oct 2, 2026

Use to test whether an AI agent, prompt, or skill actually works before or after it ships — build a small eval set, score runs, and catch regressions when the prompt or model changes. Trigger when the user asks whether a prompt is good, wants to compare models or versions, sees inconsistent agent output, or is about to put an agent in front of customers.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills352Updated Oct 2, 2026

Deploys swarms of sub-agents for massive parallel data processing tasks. Unlike agent-army (which is for code changes), this is for DATA tasks -- processing 1000 documents, analyzing datasets, bulk content generation. Configurable swarm size, task distribution, result aggregation, progress tracking, and error recovery.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills352Updated Oct 2, 2026

Designs and deploys custom agent teams for specific business workflows. Interactive discovery of business processes, then generates complete team configurations with specialized agent roles, tool access, communication protocols, and handoff rules.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills352Updated Oct 2, 2026

Agent-to-Agent (A2A) communication protocol. Connect two or more Claude agents that pass messages, share context, delegate tasks, and collaborate. Implements structured handoffs, shared memory, and multi-agent conversations.

The English summary is being prepared. Showing the original description.

OneWave-AI/claude-skills352Updated Oct 2, 2026

See all skills by OneWave-AI

Report a problem with this skill