[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71MDWMPENKX4EBN3003P505":3,"skill-same:01M71MDWMPENKX4EBN3003P505":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M71MDWMPENKX4EBN3003P505","business-pulse",null,"Produces a one-page cross-functional business snapshot for SMB owners — cash position (the ledger: MYOB, NetSuite, QuickBooks, Xero, or Zoho Books), sales trend (PayPal\u002FSquare\u002FStripe), pipeline movement (HubSpot), this week's commitments (Calendar), urgent watch-list items (Gmail or M365, Slack), and the single most important thing needing attention today. Proactively tries every available connector and gracefully scopes to whatever is connected — one connector gives a partial pulse; the full stack gives the full picture. Trigger when the user asks how the business is doing, wants a snapshot, a daily brief, a Friday recap, or says anything like \"what am I missing\" or \"catch me up on the business.\" A start-of-week briefing routes to \u002Fmonday-brief, which runs this skill as its first link.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"pulse","business","business pulse","list","start","gmail","snapshot","square","how","slack","one-page","xero","functional","stack","smb","daily brief","m365","knowledge","which","list items","2026-11-10 10:56:23",false,"---\nname: business-pulse\ndescription: \"Produces a one-page cross-functional business snapshot for SMB owners — cash position (the ledger: MYOB, NetSuite, QuickBooks, Xero, or Zoho Books), sales trend (PayPal\u002FSquare\u002FStripe), pipeline movement (HubSpot), this week's commitments (Calendar), urgent watch-list items (Gmail or M365, Slack), and the single most important thing needing attention today. Proactively tries every available connector and gracefully scopes to whatever is connected — one connector gives a partial pulse; the full stack gives the full picture. Trigger when the user asks how the business is doing, wants a snapshot, a daily brief, a Friday recap, or says anything like \\\"what am I missing\\\" or \\\"catch me up on the business.\\\" A start-of-week briefing routes to \u002Fmonday-brief, which runs this skill as its first link.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"small-business\u002Fskills\u002Fbusiness-pulse\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# Business Pulse\n\nOne 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.\n\n## Step 1 — Pull data in parallel\n\n**Dispatch all connector calls in a single parallel batch** — see `reference\u002Fdata_sources.md` for the exact tool-to-metric mapping. Do not pull serially; latency turns a 30-second skill into a painful wait.\n\nConnectors to attempt simultaneously:\n\n- **QuickBooks** — cash balance, MTD revenue, outstanding receivables, overdue invoices\n- **Xero** — same ledger read for Xero shops: cash position, receivables, P&L trend\n- **Zoho Books** — same ledger read for Zoho shops: bank balances, invoiced revenue, overdue invoices (no P&L endpoint, so the revenue line is invoiced revenue and says so)\n- **PayPal \u002F Square** — 7-day settlements, sales trend, failed\u002Fpending transactions\n- **Stripe** — settlements and sales trend, failed payments, and any new disputes — a fresh dispute goes straight to the watch list (if connected)\n- **Ramp** — company card spend for the week and the account balance, read-only (if connected)\n- **Gusto** — next payroll run date and amount, the week's biggest cash commitment (if connected)\n- **TikTok Ads** — last week's ad spend, results, and cost per result, so paid spend shows up next to the sales it claims to drive (if connected)\n- **Expensify** — last week's card spend and any expenses missing receipts, read-only, so spending surprises surface before the month-end scramble (if connected)\n- **HubSpot** — pipeline by stage, deals moved\u002Fclosed, deals gone cold, new leads\n- **Google Calendar** — key meetings, deadlines, events this week and next 7 days\n- **Gmail or Microsoft 365** — threads flagged urgent, customer complaints, time-sensitive requests\n- **Slack \u002F Teams** — urgent internal signals, threads needing owner attention\n- **RingEx Chat** — the same internal-signal read for RingEx shops: urgent team-chat posts needing the owner (if connected)\n- **DocuSign** — envelopes sitting unsigned, flagged once they are more than a few days old — money waiting on a signature (if connected)\n- **Zoho Desk** — open tickets, escalations (if connected)\n- **Shopify** — orders, revenue, sales trend, and fulfillment issues, so a commerce business sees its actual day (if connected)\n- **Square** — fulfillment issues (if connected)\n\nIf a connector errors or returns no data, record it internally and move on. Never block the pulse on a single bad integration.\n\n**QuickBooks fallback**: if QBO returns an unexpected state (account not connected, sync pending, empty response), mark the Cash section \"n\u002Fa — QuickBooks unavailable\" and proceed. Do not retry or ask the user to reconnect.\n\n**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.\n\n**Nothing connected at all is a supported path, not a failure.** If every connector is unavailable, don't stop and don't tell the owner to go connect things. Ask once, in one short message, for the handful of numbers that carry the pulse:\n\n- Cash in the bank right now, and roughly what it was a week ago\n- Anything overdue — invoices owed to them, bills they owe\n- Sales this week versus a normal week, even roughly\n- Anything already worrying them this week\n\nBuild the same one-page pulse from those answers, label the source line \"owner-supplied, not pulled,\" and skip any section they had no number for. If they'd rather not type numbers, point them at the siblings that run off a file export instead — `cash-flow-snapshot` and `report-builder` both take a CSV — and say plainly that gives a partial picture, not the full one.\n\n## Step 2 — Compute metrics\n\nRead `reference\u002Fthresholds.md` for red\u002Fyellow\u002Fgreen cutoffs. Compute:\n\n- **AR aging** — open QuickBooks invoices grouped by days since due date (0–30, 31–60, 61+)\n- **Pipeline coverage** — HubSpot weighted pipeline ÷ monthly revenue target\n- **Revenue trend** — this month's QBO revenue vs. prior month (or 7-day PayPal\u002FSquare vs. prior 7 days)\n\nAssign a 🟢\u002F🟡\u002F🔴 status to each section. If a source returned nothing, mark the metric \"n\u002Fa\" and note it in the appendix.\n\n## Step 3 — Flag risks proactively\n\nScan for actionable items. Every risk entry must name a specific record and a next step — \"some overdue invoices\" is useless; \"USD 3,400 from Acme Corp, 47 days overdue, no response since Mar 12\" is actionable.\n\n- Ledger invoices past due > 30 days — name customer, amount, days overdue\n- HubSpot deals with no activity in 7+ days, or close date in past but still open\n- Mail threads marked urgent or containing \"escalation,\" \"complaint,\" \"cancel,\" \"refund\"\n- Failed or pending PayPal\u002FSquare\u002FStripe transactions above the threshold in `reference\u002Fthresholds.md` (200 in the business's currency)\n\n## Step 4 — Compose the output\n\nUse the exact template in `reference\u002Foutput_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.\n\nCross-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.\n\nWriting rules:\n- Numbers lead, words follow. Never write \"revenue is healthy\" — write \"USD 43k this month, ▲ 8% MoM\" and let the owner judge.\n- Every number carries a delta vs. the prior period where available. Absolute snapshots (cash balance) still show WoW delta.\n- Names and dollars, not adjectives. \"USD 4,200 from Acme, 23 days overdue\" beats \"some concerning receivables.\"\n- No filler. If a section has nothing worth reporting, write \"No material changes\" and move on.\n\n## Step 5 — Deliver the pulse page\n\nAlongside the chat pulse — never instead of it — deliver the full pulse per\nthe owner's stored output preference — never default to a markdown file.\nCheck the `## Business context` block's `Output preference` (shared style\nguide rule, `..\u002F..\u002Fshared\u002Fartifact-style.md`):\n\n- **Visual artifact (the default):** render the pulse as an HTML page in the\n  house style. Cash balance, MTD revenue, and weighted pipeline are stat tiles\n  with their deltas as context lines; each section's 🟢\u002F🟡\u002F🔴 becomes a status\n  pill (good, warn, critical); the watch-list risks are a table with\n  tabular-nums amount columns; the #1 Priority gets its own panel at the top;\n  unavailable connectors go in one quiet appendix line.\n- **docx \u002F md \u002F notion \u002F canva preference:** deliver the same content in that\n  form — a DOCX or markdown file, a Notion page created via the connector\n  (named destination, never overwriting), or a Canva Doc created via the Canva\n  connector (a new design each run, named with the date; tables become\n  lists); fall back to the visual artifact if Notion or Canva is not\n  connected — and say that is why.\n- **Best for skill:** use the visual artifact — a pulse is scanned, not filed.\n\n## Step 6 — Export and share (once)\n\nAfter presenting the pulse, offer once:\n- \"Want me to save this as a file?\" (use Files connector if available — this means a copy in their drive, not a second HTML download beside the artifact)\n- \"Should I post this to your Slack?\" (only if Slack is connected and the user confirms — Slack write requires explicit approval)\n\nIf they say yes, do it. If they say no or don't respond, move on — don't ask again.\n\n## After the run\n\nClose with one line on what the pulse covered, then the single most relevant\nnext step and at most two others nearby:\n\n- If cash or AR flagged red: \"who owes me money\" runs `invoice-chase`.\n- If growth questions dominate: \"is my marketing working\" runs `growth-pulse`.\n- To make this recurring: \"Monday brief\" runs `\u002Fmonday-brief` every week.\n\nMax three offers. Never repeat an offer the owner declined this session.\n\n## Scope variants\n\nThe owner may ask for a narrower cut:\n\n- **\"Just cash\" \u002F \"financial check\"** → only Cash & Finance + AR-related risks\n- **\"Pipeline only\" \u002F \"deals check\"** → only Pipeline section + stalled-deal risks\n- **\"Watch list\" \u002F \"anything urgent\"** → only Watch List + all risks, no metric sections\n- **\"Quick snapshot before a call\"** → TL;DR + #1 Priority only, no full sections\n\n## What not to do\n\n- **Do not ask permission before pulling data.** If the skill was invoked, run it. Asking \"should I check QuickBooks?\" defeats the whole point.\n- **Do not invent or estimate numbers.** If a source returned nothing, say \"n\u002Fa\" explicitly. Never fill a gap with guesswork.\n- **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.\n- **Do not surface connector errors mid-pulse.** Log them to the appendix. The pulse leads with what was delivered.\n- **Do not trust a QuickBooks summary object.** Expenses, margin, and AP aging buckets come from the rows or the detail call (`..\u002F..\u002Fshared\u002Fquickbooks-report-traps.md`).\n\n## More sources, and scheduled presets\n\nRead `reference\u002Fv2_sources.md` for the mapping:\n\n- **Shopify** — orders, revenue, and fulfillment status, so a commerce business sees its actual day in the pulse\n- **Any ledger** — MYOB, NetSuite, QuickBooks, Xero, or Zoho Books feed the Cash & Finance section; they are peers (`..\u002F..\u002Fshared\u002Fconnector-neutrality.md`). With two connected, the owner names one as the source of record for totals\n\nThe pulse still builds from whatever is connected and degrades gracefully — one connector gives a partial pulse, the full stack gives the full picture.\n\n### Scheduled presets\n\nThis skill is schedulable, and the preset decides the shape:\n\n| Preset | When | Shape |\n|---|---|---|\n| Monday | Start of week | Full pulse, forward-looking. What's coming and what needs attention |\n| Friday | End of week | Recap. What moved, what closed, what slipped |\n\nScheduling is a property of this skill, not a reason for a separate command.\n\nOffer a cadence once, after a pulse the owner found useful. Don't ask twice.\n\n## Reference files\n\n- `reference\u002Fdata_sources.md` — exact connector tool → metric mapping with fallbacks\n- `reference\u002Fthresholds.md` — 🟢\u002F🟡\u002F🔴 cutoffs, tunable per owner\n- `reference\u002Foutput_template.md` — exact markdown structure; do not deviate\n- `reference\u002Fgotchas.md` — known failure modes (QB states, Gmail auth, Slack write)\n\n## Using a tool that isn't listed\n\nThe 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.\n","# Business Pulse\n\nOne 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.\n\n## Step 1 — Pull data in parallel\n\n**Dispatch all connector calls in a single parallel batch** — see `reference\u002Fdata_sources.md` for the exact tool-to-metric mapping. Do not pull serially; latency turns a 30-second skill into a painful wait.\n\nConnectors to attempt simultaneously:\n\n- **QuickBooks** — cash balance, MTD revenue, outstanding receivables, overdue invoices\n- **Xero** — same ledger read for Xero shops: cash position, receivables, P&L trend\n- **Zoho Books** — same ledger read for Zoho shops: bank balances, invoiced revenue, overdue invoices (no P&L endpoint, so the revenue line is invoiced revenue and says so)\n- **PayPal \u002F Square** — 7-day settlements, sales trend, failed\u002Fpending transactions\n- **Stripe** — settlements and sales trend, failed payments, and any new disputes — a fresh dispute goes straight to the watch list (if connected)\n- **Ramp** — company card spend for the week and the account balance, read-only (if connected)\n- **Gusto** — next payroll run date and amount, the week's biggest cash commitment (if connected)\n- **TikTok Ads** — last week's ad spend, results, and cost per result, so paid spend shows up next to the sales it claims to drive (if connected)\n- **Expensify** — last week's card spend and any expenses missing receipts, read-only, so spending surprises surface before the month-end scramble (if connected)\n- **HubSpot** — pipeline by stage, deals moved\u002Fclosed, deals gone cold, new leads\n- **Google Calendar** — key meetings, deadlines, events this week and next 7 days\n- **Gmail or Microsoft 365** — threads flagged urgent, customer complaints, time-sensitive requests\n- **Slack \u002F Teams** — urgent internal signals, threads needing owner attention\n- **RingEx Chat** — the same internal-signal read for RingEx shops: urgent team-chat posts needing the owner (if connected)\n- **DocuSign** — envelopes sitting unsigned, flagged once they are more than a few days old — money waiting on a signature (if connected)\n- **Zoho Desk** — open tickets, escalations (if connected)\n- **Shopify** — orders, revenue, sales trend, and fulfillment issues, so a commerce business sees its actual day (if connected)\n- **Square** — fulfillment issues (if connected)\n\nIf a connector errors or returns no data, record it internally and move on. Never block the pulse on a single bad integration.\n\n**QuickBooks fallback**: if QBO returns an unexpected state (account not connected, sync pending, empty response), mark the Cash section \"n\u002Fa — QuickBooks unavailable\" and proceed. Do not retry or ask the user to reconnect.\n\n**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.\n\n**Nothing connected at all is a supported path, not a failure.** If every connector is unavailable, don't stop and don't tell the owner to go connect things. Ask once, in one short message, for the handful of numbers that carry the pulse:\n\n- Cash in the bank right now, and roughly what it was a week ago\n- Anything overdue — invoices owed to them, bills they owe\n- Sales this week versus a normal week, even roughly\n- Anything already worrying them this week\n\nBuild the same one-page pulse from those answers, label the source line \"owner-supplied, not pulled,\" and skip any section they had no number for. If they'd rather not type numbers, point them at the siblings that run off a file export instead — `cash-flow-snapshot` and `report-builder` both take a CSV — and say plainly that gives a partial picture, not the full one.\n\n## Step 2 — Compute metrics\n\nRead `reference\u002Fthresholds.md` for red\u002Fyellow\u002Fgreen cutoffs. Compute:\n\n- **AR aging** — open QuickBooks invoices grouped by days since due date (0–30, 31–60, 61+)\n- **Pipeline coverage** — HubSpot weighted pipeline ÷ monthly revenue target\n- **Revenue trend** — this month's QBO revenue vs. prior month (or 7-day PayPal\u002FSquare vs. prior 7 days)\n\nAssign a 🟢\u002F🟡\u002F🔴 status to each section. If a source returned nothing, mark the metric \"n\u002Fa\" and note it in the appendix.\n\n## Step 3 — Flag risks proactively\n\nScan for actionable items. Every risk entry must name a specific record and a next step — \"some overdue invoices\" is useless; \"USD 3,400 from Acme Corp, 47 days overdue, no response since Mar 12\" is actionable.\n\n- Ledger invoices past due > 30 days — name customer, amount, days overdue\n- HubSpot deals with no activity in 7+ days, or close date in past but still open\n- Mail threads marked urgent or containing \"escalation,\" \"complaint,\" \"cancel,\" \"refund\"\n- Failed or pending PayPal\u002FSquare\u002FStripe transactions above the threshold in `reference\u002Fthresholds.md` (200 in the business's currency)\n\n## Step 4 — Compose the output\n\nUse the exact template in `reference\u002Foutput_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.\n\nCross-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.\n\nWriting rules:\n- Numbers lead, words follow. Never write \"revenue is healthy\" — write \"USD 43k this month, ▲ 8% MoM\" and let the owner judge.\n- Every number carries a delta vs. the prior period where available. Absolute snapshots (cash balance) still show WoW delta.\n- Names and dollars, not adjectives. \"USD 4,200 from Acme, 23 days overdue\" beats \"some concerning receivables.\"\n- No filler. If a section has nothing worth reporting, write \"No material changes\" and move on.\n\n## Step 5 — Deliver the pulse page\n\nAlongside the chat pulse — never instead of it — deliver the full pulse per\nthe owner's stored output preference — never default to a markdown file.\nCheck the `## Business context` block's `Output preference` (shared style\nguide rule, `..\u002F..\u002Fshared\u002Fartifact-style.md`):\n\n- **Visual artifact (the default):** render the pulse as an HTML page in the\n  house style. Cash balance, MTD revenue, and weighted pipeline are stat tiles\n  with their deltas as context lines; each section's 🟢\u002F🟡\u002F🔴 becomes a status\n  pill (good, warn, critical); the watch-list risks are a table with\n  tabular-nums amount columns; the #1 Priority gets its own panel at the top;\n  unavailable connectors go in one quiet appendix line.\n- **docx \u002F md \u002F notion \u002F canva preference:** deliver the same content in that\n  form — a DOCX or markdown file, a Notion page created via the connector\n  (named destination, never overwriting), or a Canva Doc created via the Canva\n  connector (a new design each run, named with the date; tables become\n  lists); fall back to the visual artifact if Notion or Canva is not\n  connected — and say that is why.\n- **Best for skill:** use the visual artifact — a pulse is scanned, not filed.\n\n## Step 6 — Export and share (once)\n\nAfter presenting the pulse, offer once:\n- \"Want me to save this as a file?\" (use Files connector if available — this means a copy in their drive, not a second HTML download beside the artifact)\n- \"Should I post this to your Slack?\" (only if Slack is connected and the user confirms — Slack write requires explicit approval)\n\nIf they say yes, do it. If they say no or don't respond, move on — don't ask again.\n\n## After the run\n\nClose with one line on what the pulse covered, then the single most relevant\nnext step and at most two others nearby:\n\n- If cash or AR flagged red: \"who owes me money\" runs `invoice-chase`.\n- If growth questions dominate: \"is my marketing working\" runs `growth-pulse`.\n- To make this recurring: \"Monday brief\" runs `\u002Fmonday-brief` every week.\n\nMax three offers. Never repeat an offer the owner declined this session.\n\n## Scope variants\n\nThe owner may ask for a narrower cut:\n\n- **\"Just cash\" \u002F \"financial check\"** → only Cash & Finance + AR-related risks\n- **\"Pipeline only\" \u002F \"deals check\"** → only Pipeline section + stalled-deal risks\n- **\"Watch list\" \u002F \"anything urgent\"** → only Watch List + all risks, no metric sections\n- **\"Quick snapshot before a call\"** → TL;DR + #1 Priority only, no full sections\n\n## What not to do\n\n- **Do not ask permission before pulling data.** If the skill was invoked, run it. Asking \"should I check QuickBooks?\" defeats the whole point.\n- **Do not invent or estimate numbers.** If a source returned nothing, say \"n\u002Fa\" explicitly. Never fill a gap with guesswork.\n- **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.\n- **Do not surface connector errors mid-pulse.** Log them to the appendix. The pulse leads with what was delivered.\n- **Do not trust a QuickBooks summary object.** Expenses, margin, and AP aging buckets come from the rows or the detail call (`..\u002F..\u002Fshared\u002Fquickbooks-report-traps.md`).\n\n## More sources, and scheduled presets\n\nRead `reference\u002Fv2_sources.md` for the mapping:\n\n- **Shopify** — orders, revenue, and fulfillment status, so a commerce business sees its actual day in the pulse\n- **Any ledger** — MYOB, NetSuite, QuickBooks, Xero, or Zoho Books feed the Cash & Finance section; they are peers (`..\u002F..\u002Fshared\u002Fconnector-neutrality.md`). With two connected, the owner names one as the source of record for totals\n\nThe pulse still builds from whatever is connected and degrades gracefully — one connector gives a partial pulse, the full stack gives the full picture.\n\n### Scheduled presets\n\nThis skill is schedulable, and the preset decides the shape:\n\n| Preset | When | Shape |\n|---|---|---|\n| Monday | Start of week | Full pulse, forward-looking. What's coming and what needs attention |\n| Friday | End of week | Recap. What moved, what closed, what slipped |\n\nScheduling is a property of this skill, not a reason for a separate command.\n\nOffer a cadence once, after a pulse the owner found useful. Don't ask twice.\n\n## Reference files\n\n- `reference\u002Fdata_sources.md` — exact connector tool → metric mapping with fallbacks\n- `reference\u002Fthresholds.md` — 🟢\u002F🟡\u002F🔴 cutoffs, tunable per owner\n- `reference\u002Foutput_template.md` — exact markdown structure; do not deviate\n- `reference\u002Fgotchas.md` — known failure modes (QB states, Gmail auth, Slack write)\n\n## Using a tool that isn't listed\n\nThe 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.\n",{"name":5,"tags":44,"tools":45,"source":46,"license":14,"description":7,"source_path":47,"source_commit":48},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","small-business\u002Fskills\u002Fbusiness-pulse","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add monoes\u002Fmonomind --skill business-pulse",{"tool":64,"command":65},"bunx","bunx skills add monoes\u002Fmonomind --skill business-pulse",{"tool":67,"command":68},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill business-pulse","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002FSKILL.md",true,[72,77,83,87,91,95],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"reference\u002Fdata_sources.md","REFERENCE","参考文档",9630,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002Freference\u002Fdata_sources.md",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"reference\u002Fgotchas.md",3193,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002Freference\u002Fgotchas.md",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"reference\u002Foutput_template.md",4062,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002Freference\u002Foutput_template.md",{"path":92,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":93,"sourceHtmlUrl":94},"reference\u002Fthresholds.md",2210,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002Freference\u002Fthresholds.md",{"path":96,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":97,"sourceHtmlUrl":98},"reference\u002Fv2_sources.md",3367,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fbusiness-pulse\u002Freference\u002Fv2_sources.md",[100,127,164,191,216,243],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":126},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[107,108,109,110,111,112,113,36,114,115,116,117,118,119,120,121,122,123,124,125],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":131,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":145,"publishedAt":126},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[135,140],{"categoryNo":136,"categoryName":137,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":141,"categoryName":142,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[146,147,148,111,149,150,151,152,115,153,154,155,156,157,158,159,160,161,162,163],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":174,"publishedAt":126},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[171],{"categoryNo":172,"categoryName":173,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000031","产品经理",[157,175,176,177,178,36,179,151,180,181,182,156,183,184,185,186,187,188,189,190],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":195,"sourceHtmlUrl":196,"categories":197,"keywords":201,"publishedAt":126},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[198],{"categoryNo":199,"categoryName":200,"taxonomyType":143,"taxonomyTypeDesc":144},"01JBSEEDCAT000000000000033","数据分析师",[115,157,202,203,204,205,36,189,151,206,207,208,209,182,210,211,212,213,214,215],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":228,"publishedAt":126},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":226,"categoryName":227,"taxonomyType":138,"taxonomyTypeDesc":139},"01JBSEEDCAT000000000000023","Skill与智能体开发",[229,230,231,232,204,233,234,235,236,114,237,238,239,115,118,210,240,241,242,212],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":247,"categories":248,"keywords":250,"publishedAt":126},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[249],{"categoryNo":226,"categoryName":227,"taxonomyType":138,"taxonomyTypeDesc":139},[231,251,252,253,254,255,256,204,257,258,153,259,260,261,118,210,262,263,212,264],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]