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 的更多技能

access
anthropic
管理 Discord 頻道存取權限 — 核准配對、編輯允許清單、設定私訊/群組政策。當使用者要求配對、核准某人、查詢誰被允許時使用…
official
session-report
anthropic
從 ~/.claude/projects 的對話記錄中,生成一份可探索的 HTML 報告,內容涵蓋 Claude Code 工作階段的使用情況(包含 token、快取、子代理、技能及高成本提示)。
official
build-mcp-server
anthropic
當使用者要求「建立 MCP 伺服器」、「建立 MCP」、「製作 MCP 整合」、「為 Claude 包裝 API」、「暴露工具給…」時,應使用此技能。
official
cookbook-audit
anthropic
根據評分標準審核 Anthropic Cookbook 筆記本。每當要求進行筆記本審查或審核時使用。
official
handle-complaint
anthropic
處理進線客戶投訴的完整流程——提取背景資訊、草擬回覆,並建議營運改善方案。可接受選填的電子郵件或工單編號……
official
use-case-triage
anthropic
快速判斷某項處理活動是否需要PIA、強制性的GDPR DPIA,或可直接進行——揭露隱私政策衝突,並引導至正確的…
official
board-minutes
anthropic
根據您指定的格式,自動草擬董事會或委員會會議記錄。自動從您的日曆中偵測即將召開的董事會及委員會會議,詢問議程及…
official
renewal-tracker
anthropic
顯示即將到來的取消截止日期的合約,並在通知窗口關閉前發出警告,依據維護中的續約登記表進行操作。當用戶詢問時使用…
official