agentsclimarketplace

Business pulse

Skill Jylhis/skills/skills/business/business-pulse

Curated Agent Skills marketplace for Claude Code, Codex, and Google Antigravity.

Install
npx -y skills add Jylhis/skills --skill business-pulse

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Produces a one-page cross-functional business snapshot for SMB owners — cash position (QuickBooks), sales trend (PayPal/Square), pipeline movement (HubSpot), this week's commitments (Calendar), urgent watch-list items (Gmail/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 weekly summary, a Monday brief, or says anything like "what am I missing" or "catch me up on the business."

SKILL.md

6.3 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

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

Dispatch all connector calls in a single parallel batch — see references/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.

Step 2 — Compute metrics

Read references/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.

Step 3 — Flag risks proactively

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

Step 4 — Compose the output

Use the exact template in references/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 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

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.

Reference files

  • references/data_sources.md — exact connector tool → metric mapping with fallbacks
  • references/thresholds.md — 🟢/🟡/🔴 cutoffs, tunable per owner
  • references/output_template.md — exact markdown structure; do not deviate
  • references/gotchas.md — known failure modes (QB states, Gmail auth, Slack write)

Gives 0 of the 12 instructions most sales crm skills give in ~1.3k tokens

Counted across 361 of the 361 authors here whose files we hold, read 2026-08-06

  • Read product marketing context before writing if it existsin 22 of 361, across 14 files
  • keep the ask low-frictionin 16 of 361, across 7 files
  • Call RUBE_SEARCH_TOOLS firstin 15 of 361, across 5 files
  • personalize every outbound messagein 13 of 361, across 4 files
  • confirm connection status is activein 13 of 361, across 4 files
  • Keep forwardable blurbs under 100 wordsin 13 of 361, across 4 files
  • State if personalization context is missingin 13 of 361, across 4 files
  • Cut any sentence that does not drive a replyin 13 of 361, across 4 files
  • Use proof instead of adjectivesin 12 of 361, across 3 files
  • Use a single, low-friction call to actionin 12 of 361, across 4 files
  • Calibrate tone to the specific audiencein 12 of 361, across 3 files
  • Make each follow-up email add new valuein 12 of 361, across 6 files

Said here and by no other author read

  • dispatch all connector calls in a single parallel batch
  • move on if a connector errors or returns no data
  • compute metrics using threshold cutoffs
  • assign a green, yellow, or red status to each section
  • name a specific record and next step for every risk
  • omit headers for connectors that lack real data

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.