content-strategy

作成者: anthropic

PayPalとQuickBooksの売上データを分析し、好調な商品と低調な商品を特定、季節性を加味した上で、優先順位付けされた30日間のコンテンツブリーフを作成します…

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill content-strategy

Content Strategy

Status: MVP draft Owner: JJ Version: 0.2.0 · Phase MVP Category: Marketing & Sales

Quick start

When an SMB owner asks "what should I post this month?" or "what's my content plan?", this skill:

  1. Pulls sales data from QuickBooks or PayPal (transaction history, product/service revenue by date)
  2. Identifies patterns — top-selling products, slow movers, seasonal trends
  3. Layers in context — seasonality (user-provided or industry benchmarks), past performance
  4. Produces a 30-day brief — ranked recommendations of what to push, what to hold, what offers to consider
  5. Gets owner approval before the brief feeds into canva-creator for asset generation

The output is strategic only — no calendar scheduling, no creative assets.


Workflow

Step 1: Pre-flight check (QuickBooks only)

If using QuickBooks, verify the business profile is set up:

  1. Call company-info to check if Industry is populated
  2. If missing or "Unknown":
    • Ask: "I need your business category to pull the right seasonality benchmarks. What industry are you in?" (e.g., retail, services, SaaS)
    • Call quickbooks-profile-info-update with the user's industry
    • Confirm: "Profile updated. Ready to pull your sales data."
  3. If profile is set, proceed to Step 2

Note: PayPal and Square do not require profile setup.

Step 2: Clarify priorities & metrics

When triggered, ask the user:

  • "How do you want me to measure 'top performers'?"

    • By total revenue?
    • By profit margin?
    • By sales velocity (how fast they're selling)?
    • Combination of the above?
  • "Do you have seasonality patterns in mind?"

    • If yes: "Tell me about them" (capture user's known seasonality)
    • If no: "I'll use industry benchmarks for your category"

Step 3: Pull and analyze sales data

Fetch data from the authenticated connector (QuickBooks, PayPal, or Square, user's choice):

  • Date range: Last 90 days (or full history if <90 days available)
  • Extract: Product/service name, date sold, revenue, quantity

Connector-specific notes:

  • QuickBooks: Fetch invoice line items via profit-loss-quickbooks-account (pre-flight sets industry context)
  • PayPal: Fetch merchant transactions via list_transactions. Rate-limiting: If you hit rate limits, pause 30 seconds and retry once. If still blocked, gracefully offer: "PayPal is rate-limited. Would you like to switch to QuickBooks or Square instead, or I can continue with historical data I already pulled?"
  • Square: Requires location ID first. Call make_api_request(service="locations", method="list") to discover available locations, then fetch orders for each location. Future enhancement: Square integration is stubbed; full path documented in reference/square-integration.md.

Fallback: If <3 months of data, use industry seasonality benchmarks for the SMB's category (e.g., retail, services, e-commerce)

Identify:

  • Top 3–5 performers (by user's chosen metric)
  • Bottom 3–5 slow movers (consider holding or repositioning)
  • Trending up (gaining momentum in last 30 days)
  • Trending down (losing momentum)

Step 4: Layer in seasonality

  • User-provided: If they shared seasonal patterns, weight recommendations against them
  • Industry benchmarks: For categories without strong user data (e.g., "Q1 is strong for tax services")
  • Timing: Flag products that should ramp up/down in the next 30 days based on seasonal patterns

Step 5: Build the 30-day brief

Structure:

  • Executive summary (1–2 sentences: "Your best sellers are X and Y. Seasonal shift to Z is starting.")
  • Push hard (Top 2–3 products + recommended content angle, e.g., "Case study on ROI", "How-to video")
  • Hold steady (Middle performers; maintain visibility but no heavy lift)
  • Reposition or pause (Slow movers; consider discounting, bundling, or pausing)
  • Seasonal opportunities (What's coming next month that you should position for now)
  • Recommended offers (Bundle, discount, or free-trial strategy based on data)

Example length: 200–400 words (brief and actionable, not essay-length).

Step 6: Owner approval & iteration

Present the brief to the owner. Ask:

  • "Does this match your gut?"
  • "Anything to adjust?"
  • "Ready to feed this to canva-creator for asset generation?"

Iterate if needed; once approved, return the final brief as structured JSON (ready for downstream tools).


Gotchas & edge cases

See reference/gotchas.md for common pitfalls.


Examples

See reference/examples/ for worked examples (SaaS, retail, services).

anthropicのその他のスキル

analyzing-financial-statements
anthropic
このスキルは、財務諸表データから投資分析のための主要な財務比率や指標を計算します。
applying-brand-guidelines
anthropic
このスキルは、生成されるすべてのドキュメントに一貫したコーポレートブランディングとスタイリング(色、フォント、レイアウト、メッセージングを含む)を適用します。
creating-financial-models
anthropic
このスキルは、DCF分析、感応度テスト、モンテカルロシミュレーション、および投資のためのシナリオプランニングを備えた高度な財務モデリングスイートを提供します…
board-minutes
anthropic
取締役会や委員会の議事録を自社のフォーマットで草稿します。カレンダーから今後の取締役会や委員会の会議を自動検出し、議題などを尋ねます…
crm-cleanup
anthropic
HubSpot内の古い商談、重複した連絡先、欠落フィールドをスキャンし、所有者が承認したものを修正します。オプションのスコープ引数で商談、連絡先などを指定可能。
redshift-api
anthropic
Amazon Redshiftに対してSQLを実行 — ステートメントの送信、ステータスのポーリング、結果のページング、データベース/スキーマ/テーブルの参照を行います。ユーザーが希望する場合にこれを使用してください…
ticket-deflector
anthropic
転送された顧客メールまたはチケットを読み取り、PayPalから注文/返金ステータスを、HubSpotからアカウント履歴を取得し、オーナーのトーンに合わせた返信を下書きします。
reg-feed-watcher
anthropic
規制フィードを今すぐチェックし、前回のチェック以降の新着情報を、あなたの重要度基準でフィルタリングして報告します。ユーザーが「フィードをチェックして」と言った場合に使用します。