Back to Details

business-pulse

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Business Pulse

Business Pulse

One prompt, one page. Pull live data from every connected tool, synthesize it into a single scannable brief, and surface the single most important thing to act on today. Do the work — don't ask the user to help find the data.
一次指令，一页报告。从所有已连接工具中提取实时数据，将其合成为一份易于浏览的简报，并突出显示今日最需采取行动的事项。主动完成所有工作——无需用户协助查找数据。

Step 1 — Pull data in parallel

步骤1：并行拉取数据

Dispatch all connector calls in a single parallel batch — see 
reference/data_sources.md
for the exact tool-to-metric mapping. Do not pull serially; latency turns a 30-second skill into a painful wait.
Connectors to attempt simultaneously:
  • QuickBooks — cash balance, MTD revenue, outstanding receivables, overdue invoices
  • PayPal / Square — 7-day settlements, sales trend, failed/pending transactions
  • HubSpot — pipeline by stage, deals moved/closed, deals gone cold, new leads
  • Google Calendar — key meetings, deadlines, events this week and next 7 days
  • Gmail — threads flagged urgent, customer complaints, time-sensitive requests
  • Slack / Teams — urgent internal signals, threads needing owner attention
  • Intercom / Zendesk — open tickets, escalations (if connected)
  • Shopify / Square — fulfillment issues (if connected)
If a connector errors or returns no data, record it internally and move on. Never block the pulse on a single bad integration.
QuickBooks fallback: if QBO returns an unexpected state (account not connected, sync pending, empty response), mark the Cash section "n/a — QuickBooks unavailable" and proceed. Do not retry or ask the user to reconnect.
Gmail fallback: Gmail auth is intermittently flaky. If the call errors, skip the Watch List section silently and note "Gmail unavailable" in the appendix — do not surface an error mid-pulse.
将所有连接器调用分配至单个并行批次——具体工具与指标的映射请参见
reference/data_sources.md
。请勿串行拉取数据；延迟会将原本30秒即可完成的Skill拖成漫长等待。
需同时尝试的连接器：
  • QuickBooks——现金余额、当月截至目前（MTD）收入、未收回账款、逾期发票
  • PayPal / Square——7天结算金额、销售趋势、失败/待处理交易
  • HubSpot——各阶段销售漏斗、已推进/已关闭的交易、已停滞的交易、新线索
  • Google Calendar——本周及未来7天的重要会议、截止日期、活动
  • Gmail——标记为紧急的邮件线程、客户投诉、时效性请求
  • Slack / Teams——紧急内部信号、需负责人关注的线程
  • Intercom / Zendesk——未解决工单、升级请求（若已连接）
  • Shopify / Square——履约问题（若已连接）
若某个连接器报错或未返回数据，在内部记录后继续执行。绝不能因单个集成故障而阻塞业务脉搏的生成。
QuickBooks 降级方案：若QuickBooks返回异常状态（账户未连接、同步中、空响应），将现金部分标记为“n/a — QuickBooks 不可用”并继续执行。请勿重试或要求用户重新连接。
Gmail 降级方案：Gmail认证偶尔会出现不稳定情况。若调用报错，静默跳过关注清单部分，并在附录中注明“Gmail 不可用”——切勿在业务脉搏生成过程中显示错误信息。

Step 2 — Compute metrics

步骤2：计算指标

Read 
reference/thresholds.md
for red/yellow/green cutoffs. Compute:
  • AR aging — open QuickBooks invoices grouped by days since due date (0–30, 31–60, 61+)
  • Pipeline coverage — HubSpot weighted pipeline ÷ monthly revenue target
  • Revenue trend — this month's QBO revenue vs. prior month (or 7-day PayPal/Square vs. prior 7 days)
Assign a 🟢/🟡/🔴 status to each section. If a source returned nothing, mark the metric "n/a" and note it in the appendix.
请阅读
reference/thresholds.md
获取红/黄/绿阈值定义。计算以下指标：
  • 应收账款账龄——按逾期天数分组的QuickBooks未结发票（0–30天、31–60天、61天以上）
  • 销售漏斗覆盖率——HubSpot加权销售漏斗金额 ÷ 月度收入目标
  • 收入趋势——当月QuickBooks收入与上月对比（或7天PayPal/Square收入与之前7天对比）
为每个部分分配🟢/🟡/🔴状态。若某数据源未返回任何数据，标记该指标为“n/a”并在附录中注明。

Step 3 — Flag risks proactively

步骤3：主动标记风险

Scan for actionable items. Every risk entry must name a specific record and a next step — "some overdue invoices" is useless; "$3,400 from Acme Corp, 47 days overdue, no response since Mar 12" is actionable.
  • QuickBooks invoices past due > 30 days — name customer, amount, days overdue
  • HubSpot deals with no activity in 7+ days, or close date in past but still open
  • Gmail threads marked urgent or containing "escalation," "complaint," "cancel," "refund"
  • Failed or pending PayPal/Square transactions > $500
扫描可采取行动的事项。每条风险记录必须明确具体记录和下一步行动——“部分逾期发票”毫无用处；“Acme Corp欠款3400美元，逾期47天，自3月12日起未收到回复”才具备可操作性。
  • QuickBooks中逾期超过30天的发票——注明客户名称、金额、逾期天数
  • HubSpot中7天以上无活动，或截止日期已过但仍未关闭的交易
  • Gmail中标记为紧急或包含“升级”“投诉”“取消”“退款”关键词的邮件线程
  • 金额超过500美元的PayPal/Square失败或待处理交易

Step 4 — Compose the output

步骤4：生成输出内容

Use the exact template in 
reference/output_template.md
. Include only sections where real data exists — omit headers for connectors that weren't available. Adapt depth to context: a casual "how are we doing" gets a fuller report; "quick snapshot before a call" gets a tighter one.
Cross-connector synthesis is where this skill earns its keep. If a Slack message connects to a stalled HubSpot deal, surface that link in the #1 Priority section. Synthesis is what makes the pulse more useful than checking each tool separately.
Writing rules:
  • Numbers lead, words follow. Never write "revenue is healthy" — write "$43k this month, ▲ 8% MoM" and let the owner judge.
  • Every number carries a delta vs. the prior period where available. Absolute snapshots (cash balance) still show WoW delta.
  • Names and dollars, not adjectives. "$4,200 from Acme, 23 days overdue" beats "some concerning receivables."
  • No filler. If a section has nothing worth reporting, write "No material changes" and move on.
使用
reference/output_template.md
中的精确模板。仅包含存在真实数据的部分——省略未连接连接器对应的标题。根据上下文调整内容深度：若用户随口问“业务情况如何”，则提供完整报告；若用户要求“通话前快速快照”，则提供精简版内容。
跨连接器数据合成是该Skill的核心价值所在。若Slack消息与HubSpot中停滞的交易相关联，需在“头号优先事项”部分突出显示该关联。正是这种合成能力让业务脉搏比单独查看每个工具更具价值。
写作规则：
  • 数字优先，文字补充。绝不要写“收入状况良好”——应写“本月收入4.3万美元，环比增长8%”，由老板自行判断。
  • 所有可用的数字均需与上期对比。绝对快照（如现金余额）仍需显示环比（WoW）变化。
  • 明确名称和金额，避免模糊形容词。“Acme欠款4200美元，逾期23天”优于“部分令人担忧的应收账款”。
  • 无冗余内容。若某部分无值得报告的内容，写“无重大变化”即可继续。

Step 5 — Export and share (once)

步骤5：导出并分享（仅一次）

After presenting the pulse, offer once:
  • "Want me to save this as a file?" (use Files connector if available)
  • "Should I post this to your Slack?" (only if Slack is connected and the user confirms — Slack write requires explicit approval)
If they say yes, do it. If they say no or don't respond, move on — don't ask again.
展示业务脉搏后，仅询问一次：
  • “需要我将此保存为文件吗？”（若Files连接器可用则使用）
  • “需要我将此发布到你的Slack吗？”（仅在Slack已连接且用户确认后执行——Slack写入操作需明确批准）
若用户同意，则执行操作。若用户拒绝或未回应，则继续后续流程——切勿再次询问。

Scope variants

范围变体

The owner may ask for a narrower cut:
  • "Just cash" / "financial check" → only Cash & Finance + AR-related risks
  • "Pipeline only" / "deals check" → only Pipeline section + stalled-deal risks
  • "Watch list" / "anything urgent" → only Watch List + all risks, no metric sections
  • "Quick snapshot before a call" → TL;DR + #1 Priority only, no full sections
老板可能要求更聚焦的内容：
  • “仅查看现金”/“财务检查” → 仅包含现金与财务部分 + 应收账款相关风险
  • “仅查看销售漏斗”/“交易检查” → 仅包含销售漏斗部分 + 停滞交易风险
  • “关注清单”/“是否有紧急事项” → 仅包含关注清单部分 + 所有风险，无指标部分
  • “通话前快速快照” → 仅包含摘要（TL;DR）+ 头号优先事项，无完整章节

What not to do

禁止操作

  • Do not ask permission before pulling data. If the skill was invoked, run it. Asking "should I check QuickBooks?" defeats the whole point.
  • Do not invent or estimate numbers. If a source returned nothing, say "n/a" explicitly. Never fill a gap with guesswork.
  • Do not skip the delta. A number without a comparison is a missed insight. If there's no prior-period baseline, say "(no prior baseline)" rather than omitting the field.
  • Do not surface connector errors mid-pulse. Log them to the appendix. The pulse leads with what was delivered.
  • 拉取数据前请勿请求许可。若Skill已被调用，直接执行。询问“我是否应该检查QuickBooks？”完全违背了该Skill的初衷。
  • 请勿编造或估算数据。若数据源未返回任何内容，明确标注“n/a”。绝不能用猜测填补数据空白。
  • 请勿遗漏对比数据。缺乏对比的数字毫无洞察力。若无上期基准，标注“（无上期基准）”而非省略该字段。
  • 业务脉搏生成过程中请勿显示连接器错误。将错误记录在附录中。业务脉搏应优先展示已获取的有效内容。

Reference files

参考文件

  • reference/data_sources.md
    — exact connector tool → metric mapping with fallbacks
  • reference/thresholds.md
    — 🟢/🟡/🔴 cutoffs, tunable per owner
  • reference/output_template.md
    — exact markdown structure; do not deviate
  • reference/gotchas.md
    — known failure modes (QB states, Gmail auth, Slack write)
  • reference/data_sources.md
    ——精确的连接器工具→指标映射及降级方案
  • reference/thresholds.md
    ——🟢/🟡/🔴阈值定义，可根据老板需求调整
  • reference/output_template.md
    ——精确的Markdown结构；请勿随意更改
  • reference/gotchas.md
    ——已知故障模式（QuickBooks状态、Gmail认证、Slack写入）