mcpbeat

Sales Brief

anthropics/sales-brief

Surfaces top and bottom sellers, identifies seasonality patterns, and produces a 2-week content brief to push winners and clear slow movers. Accepts optional lookback window of 30, 60, or 90 days.

712 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
23273
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill sales-brief

What it tells the agent to use

found in the instruction text
WebFetch fetches pages from the network

The instruction itself

7 sections, as written by the author

Run the sales analysis and content brief. Pull what sold (and what didn't), explain why, and produce a ready-to-use content plan that acts on the data.

Parse arguments:

  • --lookback (default: 30d) — 30d, 60d, or 90d lookback window

Step 1 — Sales breakdown

Using the content-strategy skill workflow for sales analysis:

  • Pull PayPal transactions for the lookback period grouped by item/service/SKU.
  • Pull QuickBooks revenue by product/service category.
  • Rank products by: total revenue, unit volume, and margin (if available in QB).
  • Calculate each product's share of total revenue vs. prior equivalent period.

Top sellers: products that grew share or maintained top-3 rank.

Bottom sellers: products with declining volume or below 5% of revenue.

Step 2 — Seasonality check

  • Compare current period to same period in prior year (if QB history available).
  • Flag any items with a seasonal pattern (e.g., spikes in Q4, slow summers).
  • Note any new products with insufficient history to detect seasonality.

Step 3 — Why analysis

For each top and bottom seller, explain the likely driver:

  • Price change, promo, new channel, seasonal demand, competitor move
  • Cross-reference with HubSpot campaign activity for the period
  • Note where attribution is inferred vs. confirmed

Step 4 — 2-week content brief

Produce a ready-to-use content brief:

2-Week Content Brief — {date range}

PUSH THESE (winners)
• {product}: {suggested angle} — {channel: email|social|both}
• {product}: {suggested angle} — {channel}

CLEAR THESE (slow movers)
• {product}: {promo angle or bundle suggestion} — {channel}

CONTENT CALENDAR
Week 1:
  Mon: {post/email concept}
  Wed: {post/email concept}
  Fri: {post/email concept}
Week 2:
  Mon: {post/email concept}
  Wed: {post/email concept}
  Fri: {post/email concept}

Connector failures

If both QuickBooks and PayPal are unreachable, stop — sales analysis requires at least one revenue source. If only one is connected, run from that source and note "QuickBooks not connected — revenue data from PayPal only" (or vice versa). If HubSpot is missing, skip campaign cross-reference in the "why analysis" and note it.

Approval gates

  • Never auto-schedule or publish content. The brief is for owner review only.
  • Never create Canva assets automatically — offer to generate them after owner approves the brief.

Output

Present the sales analysis, then the content brief. Ask the owner if they'd like to generate Canva assets for any of the planned posts.

How to use it

Copy the folder

Take anthropics/sales-brief from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.