Focus Code Skill Marketplace

Skill Introduction

Overview

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.

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 sales-brief-316f0c

View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: sales-brief description: 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. allowed-tools: Read, WebFetch, Bash

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.

sales brief