quarterly-review
anthropics/knowledge-work-plugins
How to install quarterly-review
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill quarterly-reviewFull instructions (SKILL.md)
Source of truth, from anthropics/knowledge-work-plugins.
name: quarterly-review description: Generates a full QBR narrative — revenue trend, margin trend, customer health, top opportunities and risks — as a presentation-ready PDF or deck. Accepts optional quarter and save-to arguments. allowed-tools: Read, WebFetch, Bash
Run the quarterly business review. Pull financial, sales, and customer data for the quarter, synthesize it into a narrative, and produce a presentation-ready document.
Parse arguments:
--quarter(default: previous calendar quarter) — formatYYYY-QN(e.g.,2026-Q1)--save-to(default:files) —files(Google Drive / OneDrive),desktop, orboth
Step 1 — Financial performance
Using the business-pulse skill in deep mode:
- Pull QuickBooks P&L for the quarter: revenue, COGS, gross margin, operating expenses, net margin.
- Compare to prior quarter and same quarter last year (if available).
- Pull PayPal settlements for the same period to validate QB revenue.
- Calculate: revenue growth %, margin change in points, top 3 revenue categories.
Step 2 — Customer health
- Pull HubSpot deal data: new customers won, churned, average deal size, pipeline entering next quarter.
- Calculate customer acquisition cost (if data available) and revenue per customer.
- Flag any customers representing >20% of revenue (concentration risk).
Step 3 — Top opportunities
Identify 3 specific opportunities for next quarter based on the data:
- Revenue upside (category, customer segment, or channel to double down on)
- Margin upside (cost to cut or price to raise)
- Customer upside (segment to target or churn to reduce)
Step 4 — Top risks
Identify 3 specific risks for next quarter:
- Revenue risk (concentration, trend, seasonality)
- Margin risk (rising cost, pricing pressure)
- Operational risk (pipeline gap, vendor dependency)
Step 5 — QBR narrative
Write a 500–800 word narrative in plain business English with this structure:
- Quarter headline (one sentence)
- Revenue story (trend + why)
- Margin story (trend + why)
- Customer story (health + pipeline)
- Three opportunities
- Three risks
- One-paragraph call to action for next quarter
Step 6 — Export
Generate:
qbr-{YYYY-QN}.pdf— formatted narrative + key charts (as ASCII tables if no chart tool available)- Save to
--save-tolocation
Connector failures
If QuickBooks is unreachable, stop — the QBR requires QB financial data as the foundation. If PayPal is missing, skip cross-validation and note "PayPal not connected — revenue validated from QB only." If HubSpot is missing, skip customer health (Step 2) and note "HubSpot not connected — customer health section skipped."
Approval gates
- Never publish or email the QBR automatically. Always display for owner review first.
- Flag if any data source returns incomplete data — note gaps in the narrative.
Output
Present the narrative in-line, then confirm export. End with a one-paragraph "what to focus on next quarter" summary.
Related skills
More from anthropics/knowledge-work-plugins and the wider catalog.
data-visualization
Pick the right chart and generate publication-quality Python visualizations with built-in design and accessibility best practices.
code-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
documentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
build-dashboard
Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
task-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.