企业业务快照_business-pulse

以下为本文档的中文说明该技能为中小企业主生成一页纸的跨职能业务快照整合来自多个数据源的实时信息形成一个可快速扫描的业务简报。技能的核心能力是主动调用所有可用的数据连接器将零散的业务数据综合为有洞察力的摘要并指出当天最关键的一个行动项。技能的工作流程是并行拉取数据——一次性地从所有连接的系统中获取最新信息从QuickBooks获取现金余额、月度收入、应收款项和逾期发票从PayPal/Square获取7天结算金额、销售趋势和失败/待处理交易从HubSpot获取按阶段划分的管道、移动/关闭的交易、变冷的交易以及新线索从Google日历获取本周承诺的会议和事件从Gmail/Slack获取紧急的关注列表。所有数据收集后技能会将其综合为一页纸的快照包括现金状况仪表盘、销售趋势概览、管道健康度检查、本周关键承诺以及最需要关注的一个事项。使用场景包括每天早上获取业务概览、周一的周报生成、以及任何时候当用户询问“业务怎么样了”或“我错过了什么”时。核心原则是“不提问直接做”——技能会主动尝试每一个可用的连接器不要求用户提供数据来源有多少连接器就生成多大范围的快照而不是因为没有全部连接就放弃。技能在数据综合阶段使用了智能摘要算法不是简单罗列数据而是主动识别趋势变化和异常信号。例如它会对比本周与上周的现金余额变化趋势、标记销售额的异常波动、识别管道中长时间未推进的停滞交易、以及从通讯中提取需要紧急处理的事项。输出的业务快照采用结构化格式每个模块都有清晰的视觉分隔和关键数据突出显示让忙碌的企业主可以在30秒内掌握全貌。技能还会根据当前业务状况给出可操作的建议例如现金余额低于安全线时的节约建议、销售趋势下滑时的营销策略建议、管道中关键交易停滞时的跟进提醒等。核心设计理念是让数据为决策服务而非让用户在海量数据中自行寻找答案。Business PulseOne 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 parallelDispatch all connector calls in a single parallel batch— seereference/data_sources.mdfor 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 invoicesPayPal / Square— 7-day settlements, sales trend, failed/pending transactionsHubSpot— pipeline by stage, deals moved/closed, deals gone cold, new leadsGoogle Calendar— key meetings, deadlines, events this week and next 7 daysGmail— threads flagged urgent, customer complaints, time-sensitive requestsSlack / Teams— urgent internal signals, threads needing owner attentionIntercom / 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.Step 2 — Compute metricsReadreference/thresholds.mdfor 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 targetRevenue 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.Step 3 — Flag risks proactivelyScan 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 overdueHubSpot deals with no activity in 7 days, or close date in past but still openGmail threads marked urgent or containing “escalation,” “complaint,” “cancel,” “refund”Failed or pending PayPal/Square transactions $500Step 4 — Compose the outputUse the exact template inreference/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.Step 5 — Export and share (once)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.Scope variantsThe 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 sectionsWhat not to doDo 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.Reference filesreference/data_sources.md— exact connector tool → metric mapping with fallbacksreference/thresholds.md— // cutoffs, tunable per ownerreference/output_template.md— exact markdown structure; do not deviatereference/gotchas.md— known failure modes (QB states, Gmail auth, Slack write)