Help us improve
Share bugs, ideas, or general feedback.
From paywhere-smb
Produces a one-page cross-functional business snapshot for SMB owners — cash position (Paywhere + QuickBooks), sales trend (QuickBooks), 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."
npx claudepluginhub paywhereb/paywhere-claude-plugins --plugin paywhere-smbHow this skill is triggered — by the user, by Claude, or both
Slash command
/paywhere-smb:business-pulseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
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.
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:
list_accounts →
get_account_balance), 7-day inflow/outflow (get_account_transactions),
pending wires/ACH (get_wire_payment_status,
get_ach_payment_status). Set intent to "Producing the owner's weekly
pulse — cash position and pending money movement."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.
Read reference/thresholds.md for red/yellow/green cutoffs. Compute:
Assign a 🟢/🟡/🔴 status to each section. If a source returned nothing, mark the metric "n/a" and note it in the appendix.
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.
get_wire_payment_status / get_ach_payment_status. Flag with counterparty (from description), amount, and days outstanding past the expected window (wire same-day, ACH 1–3 business days).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:
After presenting the pulse, offer once:
If they say yes, do it. If they say no or don't respond, move on — don't ask again.
The owner may ask for a narrower cut:
reference/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)