Back to Details

marketing-monday

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Run the weekly growth briefing by chaining two skills — 
growth-pulse
for whether the engine is working and 
review-reputation
for what customers are saying — then adding a web-native competitor scan. The three parts feed one merged brief; this is not three reports stapled together.
Connectors: any one of PayPal, Shopify, or HubSpot is enough to run. Apollo, Clay, Mailchimp, Square, Stripe, and TikTok Ads each add a layer. TikTok Ads contributes the paid layer to Step 1 through growth-pulse: last week's spend, results, and cost per result beside the sales trend, reported as the platform's own claim next to the CRM's lead count, never blended (
../growth-pulse/reference/data_sources.md
). Mailchimp contributes the email channel to Step 1 (its 
get_capabilities
call needs 
user_request
and a 
category
; 
../../shared/connector-call-shapes.md
) — campaign analytics with revenue attribution and audience-growth numbers. It is read-only in this brief: nothing is drafted or sent from here, and its attributed revenue is reported as the email channel's own claim beside the platform and CRM numbers, never blended into one figure. With none of them, CSV exports and pasted reviews go in, and the competitor scan runs web-native with no connector at all.
Default window: the last 7 days for the pulse, the last 90 days for reviews, and since the last run for the competitor watchlist.
通过串联两个技能运行每周增长简报：
growth-pulse
用于判断增长引擎是否运转，
review-reputation
用于收集客户反馈，之后再加上原生网页竞品扫描。三个部分整合为一份合并简报，而非三份报告的简单拼接。
连接器：只需接入PayPal、Shopify或HubSpot其中任意一个即可运行。接入Apollo、Clay、Mailchimp、Square、Stripe和TikTok Ads可分别补充额外维度数据。TikTok Ads通过 
growth-pulse
为第一步提供付费渠道维度数据：上周支出、效果、单次效果成本，与销售趋势并列呈现；数据以平台自有统计值和CRM线索量分开展示，绝不混合计算（
../growth-pulse/reference/data_sources.md
）。Mailchimp为第一步提供邮件渠道数据（其 
get_capabilities
调用需要 
user_request
和 
category
参数，参见 
../../shared/connector-call-shapes.md
）：包含收入归因的活动分析以及受众增长数据。本简报中Mailchimp仅为只读模式：不会在此处起草或发送任何内容，其归因收入将作为邮件渠道自有统计值与平台、CRM数据并列呈现，绝不合并为单一数值。若未接入任何连接器，可导入CSV导出文件和粘贴的评论，竞品扫描则完全基于原生网页运行，无需任何连接器。
默认时间范围：
growth-pulse
数据取过去7天，评论数据取过去90天，竞品观察名单数据取上次运行至今的内容。

Step 1 — Is the engine working (growth-pulse)

步骤1 — 增长引擎是否正常运转（growth-pulse）

Trigger the 
growth-pulse
skill workflow. Pull every connector in one parallel batch; a serial run is a wait nobody sits through twice.
In: whatever is connected, or exports. Out: channel trend, funnel conversion, campaign return, product performance, and sentiment — each with a status, and anything missing marked "n/a" rather than silently dropped.
Handoff: carry forward the single sentence that explains the period, plus the biggest drop-off in the funnel and any product carrying the whole trend. Do not carry the full five-view dashboard into the merged brief.
No gate here. The command was invoked; run it. Reading data is not an approval-worthy action.
触发 
growth-pulse
技能工作流。一次性并行拉取所有连接器的数据；串行运行的等待时间没人愿意承受第二次。
输入： 所有已接入的连接器数据，或导出的文件。输出： 渠道趋势、漏斗转化、活动回报、产品表现和情感分析——每项均带有状态标识，缺失的数据标记为「n/a」而非静默忽略。
交接内容： 传递说明统计周期的单句话，以及漏斗中最大的流失环节、拉动整体趋势的核心产品。不要把完整的五视图仪表盘直接搬进合并简报。
此处无审批门槛。 命令已被调用，直接运行即可。读取数据不属于需要审批的操作。

Step 2 — What customers are saying (review-reputation)

步骤2 — 客户在说什么（review-reputation）

Trigger the 
review-reputation
skill workflow.
In: public reviews, PayPal disputes, HubSpot tickets, complaint-language email threads, and pasted or exported reviews when nothing reads them directly. Out: three to five themes with verbatim quotes, reviews needing a reply, and customers who have gone quiet.
Handoff: carry forward the themes and the rating direction. Carry the drafted replies as a separate approval queue, not as brief content.
Gate: nothing posts publicly without the owner reading it first, one review at a time. This gate survives the chain intact — a merged brief does not become blanket approval to reply on the owner's behalf.
If the quiet-customer list is worth working, point at 
/reactivate
rather than starting win-back drafts inside this brief.
触发 
review-reputation
技能工作流。
输入： 公开评论、PayPal争议、HubSpot工单、带有投诉语气的邮件线程，以及无直接读取渠道时粘贴或导出的评论。输出： 3-5个主题及原文引用、需要回复的评论、已沉默的客户列表。
交接内容： 传递评论主题和评分趋势。将草拟的回复作为单独的审批队列，而非简报内容的一部分。
审批门槛： 未经负责人逐一审核，不得公开发布任何回复。该审批门槛在整个串联流程中保持有效——合并简报不代表获得了代负责人回复的全权授权。
如果沉默客户列表值得跟进，指向 
/reactivate
指令即可，不要在本简报内起草赢回文案。

Step 3 — What competitors did (web research)

步骤3 — 竞品做了什么（网页调研）

Run this leg inline — it needs no connector. Check the owner's saved watchlist of competitors (or ask for three or four names the first time, then save them) and scan public sources: their site and pricing pages, social and ad activity, job postings, and any press. Add HubSpot win-loss notes when HubSpot is connected.
Out: what changed, with observed facts and inferences labeled separately and everything dated. Never present an inference as an observation.
Handoff: carry forward only material changes. A quiet week is reported as a quiet week — three lines, no padding. That honesty is what makes the week something real happens land hard.
Gate: nothing acts on the intel. A price move or a campaign is the owner's decision.
该步骤直接内联运行，无需连接器。检查负责人保存的竞品观察名单（首次运行时可询问3-4个竞品名称，之后保存），并扫描公开来源：竞品官网和定价页、社交和广告活动、招聘信息、所有新闻报道。若接入了HubSpot，可补充赢单/输单记录。
输出： 竞品的变化内容，其中观察到的事实和推论内容分开标注，所有内容均标注日期。绝不能把推论当作观察结果呈现。
交接内容： 仅传递实质性变化。如果本周风平浪静，就如实报告——三行字即可，不要凑内容。这种诚实才会让真正有大事发生的那周更有分量。
审批门槛： 不得基于调研情报采取任何行动。价格调整或营销活动都需要负责人决策。

Step 4 — Merge into one brief

步骤4 — 合并为一份简报

This is the step that makes the command worth having, so do not shortcut it.
The output is one page, not three sections handed over intact. Read the three inputs together and find where they explain each other. The connections that usually matter:
  • Sentiment sliding while revenue holds is the early warning that shows up in revenue two months out.
  • A competitor's price move against a product whose margin is already thin is a decision, not a note.
  • Falling win rate with strong lead volume, plus review complaints about response time, is one story told twice.
  • A quiet-customer list growing alongside a new competitor location is churn with a named cause.
Structure:
  1. Headline — the one thing that matters this week, in a sentence
  2. How growth performed — the numbers, each with its comparison
  3. What customers said — themes with verbatim quotes
  4. What changed around you — competitor moves, observed and dated
  5. Do these three things this week — exactly three, ranked by size of impact
Every action needs what to do, the number from this brief that justifies it, and roughly what it is worth. Rank by impact, not by ease — Ray Okonkwo can judge what is easy; only the brief can tell him what is big.
If the honest answer is that nothing needs to change, say that. A brief that manufactures three actions every week trains the owner to ignore all of them.
这是该命令的核心价值所在，切勿走捷径。
输出是单页内容，而非三个独立部分的简单堆砌。要综合读取三份输入，找到它们之间的关联。通常重要的关联包括：
  • 收入保持稳定但情感分析下滑，是两个月后收入下跌的早期预警信号。
  • 竞品针对某款利润已经很薄的产品调价，这是需要决策的问题，不是普通通知。
  • 线索量充足但赢单率下降，加上评论里抱怨响应速度，其实是同一个问题的两种表现。
  • 沉默客户列表增长的同时竞品新开了网点，这是有明确原因的客户流失。
简报结构：
  1. 核心头条 —— 本周最重要的一件事，用一句话概括
  2. 增长表现 —— 各项数据及对比情况
  3. 客户反馈 —— 主题及原文引用
  4. 周边竞品动态 —— 已标注日期的竞品动向，区分观察事实与推论
  5. 本周必做三项行动 —— 恰好三项，按影响大小排序
每项行动都需要说明：要做什么、本简报中支撑该行动的数据、以及大致的预期价值。按影响大小排序，而非按难易度排序——Ray Okonkwo能判断什么事容易做；只有简报能告诉他什么事价值大。
如果诚实的结论是不需要做任何改变，就直接说出来。每周硬凑三项行动的简报，只会让负责人逐渐忽略所有内容。

Step 5 — Offer the cadence, once

步骤5 — 一次性提议定期运行

Offer to run this weekly. Ask once. On a yes, set the schedule and confirm the day and time. On a no or no answer, move on and do not ask again in the same run.
Each scheduled run compares against the previous one and rolls the baseline forward, because change only means anything against a baseline.
提议每周运行该简报。只问一次。如果用户同意，就设置排期并确认运行的日期和时间。如果用户拒绝或没有回应，就继续下一步，同一次运行中不要再问。
每次定时运行都会和上一次运行结果对比，并滚动更新基准线，因为变化只有相对于基准线才有意义。

Approval gates (must hold)

审批门槛（必须严格遵守）

  • No public review response posts without per-review approval.
  • No win-back message sends from this command — that is 
    /reactivate
    .
  • No pricing or campaign action is taken on competitor intel. Recommend and stop.
  • The cadence is set only on an explicit yes.
  • If a connector fails, name it in the sources line and continue. A named gap is information; a silent one looks like good news.
  • 未经单条审核，不得发布任何公开评论回复。
  • 不得从该命令发送任何赢回消息——那是 
    /reactivate
    的功能。
  • 不得基于竞品情报采取定价或营销行动，仅提供建议即可。
  • 仅在用户明确同意时才设置定期运行。
  • 如果某个连接器失效，在来源行中明确指出并继续运行。明确的缺口是有效信息；隐而不报的缺口会让人误以为一切顺利。

What not to do

禁止行为

  • Do not staple three reports together. One merged brief with three actions at the end is the deliverable. If the output reads as a growth section, then a review section, then a competitor section with no connective sentence between them, it failed.
  • Do not pad a quiet week. "Nothing material changed" protects the credibility of the week something did.
  • Do not invent attribution or a competitor move. Both get repeated to other people.
  • Do not report CRM forecast value as revenue. Deal values are hopes; invoices are facts.
  • Do not ask about the schedule more than once.
  • Do not exceed three actions. Four is a to-do list nobody works.
  • Do not read expenses or margin from the QuickBooks P&L summary. Its 
    totalExpenses
    can be zero against real rows; total the rows or 
    monthlyBreakdown
    (
    ../../shared/quickbooks-report-traps.md
    , Trap 2).
  • 不要把三份报告简单拼接。 最终交付物是一份合并简报，末尾附三项行动。如果输出读起来是增长部分、评论部分、竞品部分各自独立，没有衔接句，那就是失败的。
  • 不要给平淡的一周凑内容。 「无实质性变化」才能保住有大事发生那周的可信度。
  • 不要编造归因结果或竞品动向。 两者都会被转述给其他人。
  • 不要把CRM预测值当作收入上报。 交易金额是预期；发票金额才是事实。
  • 不要多次询问排期设置。
  • 不要超过三项行动。 四项行动就是没人会执行的待办清单。
  • 不要从QuickBooks损益表摘要中读取费用或利润数据。 其 
    totalExpenses
    字段可能在实际有数据行的情况下显示为零；应汇总各行数据或使用 
    monthlyBreakdown
    字段（
    ../../shared/quickbooks-report-traps.md
    ，陷阱2）。

Output

输出形式

One page in chat, with the three actions last. Offer once to save it as a file or post it to Slack, then stop asking.
Also deliver the merged brief per the owner's stored output preference — never default to a markdown file. Check the 
## Business context
block's 
Output preference
(shared style guide rule, 
../../shared/artifact-style.md
):
  • Visual artifact (the default): render the brief as an HTML page in the house style. One page, mirroring the merge: growth stat tiles for the headline numbers, a sentiment-themes panel with verbatim quotes, the competitor-changes list dated and labeled observed vs. inferred, and a three-actions panel last. The chat summary stays — the artifact is additive, never the only copy.
  • docx / md / notion / canva preference: deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.
  • Best for skill: use the visual artifact — a weekly brief is scanned, not filed.
聊天窗口中输出单页简报，最后放三项行动。一次性提议将简报保存为文件或发布到Slack，之后就不要再问。
同时根据负责人保存的输出偏好交付合并简报——绝不要默认输出markdown文件。检查 
## Business context
区块中的 
Output preference
字段（共享风格指南规则，
../../shared/artifact-style.md
）：
  • 可视化产物（默认）： 按照内部统一风格将简报渲染为HTML页面。单页布局，与合并后的内容对应：核心数据用增长数据卡片展示，情感主题面板附带原文引用，竞品变化列表标注日期并区分「观察事实」与「推论」，末尾是三项行动面板。聊天中的摘要内容保留——可视化产物是补充形式，绝非唯一的内容载体。
  • docx / md / notion / canva 偏好： 以对应格式交付相同内容——DOCX或markdown文件、通过连接器创建的Notion页面（指定目标位置，绝不覆盖原有内容）、或通过Canva连接器创建的Canva Doc（每次运行生成新设计，以日期命名；表格转换为列表）；如果未接入Notion或Canva，则回退到可视化产物，并说明原因。
  • 技能最佳实践： 使用可视化产物——每周简报是用来快速浏览的，不是用来存档的。

Closing offer

收尾提议

End with one line on what was delivered — the week's headline and the three actions. Then offer the single most relevant next step with its exact trigger phrase, usually "win back quiet customers" (
/reactivate
) when the quiet-customer list is worth working. Offer at most two others drawn from the router's table, such as "what should I promote?" (
content-strategy
) or "who should I call?" (
lead-triage
). Three offers maximum, and never re-offer something the owner already declined this session.
结尾用一句话说明交付内容：本周核心头条和三项行动。然后提供一个最相关的下一步操作及其准确触发指令，通常当沉默客户列表值得跟进时，推荐「唤醒沉默客户」（
/reactivate
）。最多再从路由表中选取两个其他选项，比如「我该推广什么？」（
content-strategy
）或「我该联系谁？」（
lead-triage
）。最多提供三个提议，且绝不要重复提议本次会话中负责人已经拒绝的内容。

Using a tool that isn't listed

使用未列出的工具

The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer 
build-connector
— it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.
本技能中列出的连接器是经过测试的路径，而非限制。如果负责人希望该流程使用未接入或未列出的工具，可提供 
build-connector
技能——它会先检查连接器目录，否则通过Zapier接入，绝不对原始API进行手动开发。一旦连接完成，该工具就会像其他可选连接器一样加入本技能，遵守相同的审批门槛。