content-strategy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Content Strategy

内容策略

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

状态： MVP草稿 负责人： JJ 版本： 0.2.0 · MVP阶段 分类： 营销与销售

Quick start

快速上手

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

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

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

当中小企业主询问“我本月应该发布什么内容？”或“我的内容规划是什么？”时，该Skill会执行以下操作：

拉取销售数据：从QuickBooks或PayPal获取（交易历史、按日期统计的产品/服务收入）
识别规律——畅销产品、滞销产品、季节性趋势
结合上下文——季节性因素（用户提供或行业基准）、过往表现
生成30天简报——按优先级排序的建议：重点推广内容、暂缓内容、可考虑的优惠活动
获取负责人批准：简报获批后，才会传入
```
canva-creator
```
用于生成创意资产

输出仅包含战略层面内容——不包含日程安排或创意资产。

Workflow

工作流程

Step 1: Pre-flight check (QuickBooks only)

步骤1：预检查（仅QuickBooks适用）

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

Call
```
company-info
```
to check if
```
Industry
```
is populated
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."
If profile is set, proceed to Step 2

Note: PayPal and Square do not require profile setup.

若使用QuickBooks，需验证企业资料是否已设置：

调用
```
company-info
```
检查
```
Industry
```
字段是否已填写
若缺失或为“Unknown”：
- 询问：“我需要您的业务类别来获取合适的季节性基准数据。您所在的行业是什么？”（例如：零售、服务、SaaS）
- 调用
```
quickbooks-profile-info-update
```
  更新用户提供的行业信息
- 确认：“资料已更新。准备拉取您的销售数据。”
若资料已设置，进入步骤2

注意： PayPal和Square无需设置资料。

Step 2: Clarify priorities & metrics

步骤2：明确优先级与衡量指标

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"

触发该Skill时，询问用户：

“您希望如何衡量‘畅销品’？”
- 按总收入？
- 按利润率？
- 按销售速度（售出快慢）？
- 以上指标组合？
“您是否了解自身业务的季节性规律？”
- 若是：“请详细说明”（记录用户已知的季节性模式）
- 若否：“我将使用您所在类别的行业基准数据”

Step 3: Pull and analyze sales data

步骤3：拉取并分析销售数据

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)

从已认证的连接器（用户可选QuickBooks、PayPal或Square）获取数据：

日期范围：过去90天（若可用数据不足90天则取全部历史数据）
提取字段：产品/服务名称、售出日期、收入、数量

连接器专属说明：

QuickBooks：通过
```
profit-loss-quickbooks-account
```
获取发票明细项（预检查已设置行业上下文）
PayPal：通过
```
list_transactions
```
获取商家交易记录。速率限制： 若触发速率限制，暂停30秒后重试一次。若仍被限制，友好提示：“PayPal触发了速率限制。您是否愿意切换到QuickBooks或Square，或者我可以使用已拉取的历史数据继续分析？”
Square：需先获取位置ID。调用
```
make_api_request(service="locations", method="list")
```
发现可用位置，然后获取每个位置的订单记录。未来优化： Square集成目前为占位实现，完整流程记录在
```
reference/square-integration.md
```
中。

** fallback方案**：若可用数据不足3个月，使用中小企业所在类别的行业季节性基准数据（例如：零售、服务、电商）

识别以下内容：

3-5款畅销品（按用户选择的指标）
3-5款滞销品（考虑暂缓或重新定位）
上升趋势（过去30天销量增长）
下降趋势（过去30天销量下滑）

Step 4: Layer in seasonality

步骤4：结合季节性因素

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

用户提供的规律：若用户分享了季节性模式，以此调整建议权重
行业基准：针对用户数据不足的类别（例如：“第一季度是税务服务的旺季”）
时间节点：根据季节性模式，标记未来30天内应加大/减少推广的产品

Step 5: Build the 30-day brief

步骤5：生成30天简报

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

结构：

执行摘要（1-2句话：“您的畅销品是X和Y。即将进入Z产品的季节性增长期。”）
重点推广（2-3款核心产品 + 推荐内容角度，例如：“ROI案例研究”、“操作教学视频”）
维持现状（表现中等的产品；保持曝光但无需重点投入）
重新定位或暂缓（滞销品；考虑打折、捆绑销售或暂停推广）
季节性机遇（下月即将到来的趋势，需提前布局）
推荐优惠策略（基于数据的捆绑、折扣或免费试用方案）

示例篇幅：200-400字（简洁且具备可操作性，无需长篇大论）

Step 6: Owner approval & iteration

步骤6：负责人批准与迭代

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

向负责人展示简报，并询问：

“这份简报符合您的预期吗？”
“是否需要调整内容？”
“是否准备将简报传入canva-creator生成创意资产？”

若需调整则进行迭代；获批后，返回结构化JSON格式的最终简报（可直接用于下游工具）。

Gotchas & edge cases

注意事项与边缘情况

See

reference/gotchas.md

for common pitfalls.

详见

reference/gotchas.md

中的常见问题。

Examples

示例

See

reference/examples/

for worked examples (SaaS, retail, services).

详见

reference/examples/

中的实际案例（SaaS、零售、服务行业）。