Skill Market

quarterly review

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.

GitHub
githubcommunity
0.0
0 installs24.9K GitHub starsby anthropics

Skill Introduction

Overview
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.

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community work faster.

Target users

  • Developers, testers, and maintainers who handle Development tasks in Focus Code.
  • Teams that already trust workflows or content from anthropics.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Development, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install quarterly-review-5c070e
View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

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) — format YYYY-QN (e.g., 2026-Q1)
  • --save-to (default: files) — files (Google Drive / OneDrive), desktop, or both

Step 1 — Financial performance

Using the business-pulse skill in deep mode:

  1. Pull QuickBooks P&L for the quarter: revenue, COGS, gross margin, operating expenses, net margin.
  2. Compare to prior quarter and same quarter last year (if available).
  3. Pull PayPal settlements for the same period to validate QB revenue.
  4. Calculate: revenue growth %, margin change in points, top 3 revenue categories.

Step 2 — Customer health

  1. Pull HubSpot deal data: new customers won, churned, average deal size, pipeline entering next quarter.
  2. Calculate customer acquisition cost (if data available) and revenue per customer.
  3. 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:

  1. Quarter headline (one sentence)
  2. Revenue story (trend + why)
  3. Margin story (trend + why)
  4. Customer story (health + pipeline)
  5. Three opportunities
  6. Three risks
  7. One-paragraph call to action for next quarter

Step 6 — Export

Generate:

  1. qbr-{YYYY-QN}.pdf — formatted narrative + key charts (as ASCII tables if no chart tool available)
  2. Save to --save-to location

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.

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet