Invoice Chase

anthropics/knowledge-work-pluginsOfficial

Pulls overdue invoices from QuickBooks and optionally Stripe, cross-references PayPal settlements to avoid chasing customers who just paid, then drafts tone-matched reminder emails based on each customer's payment history. Good payers get gentle nudges, repeat offenders get firmer language. Nothing sends until you approve. PayPal invoices go out via PayPal, everything else queues as drafts in Gmail or Apple Mail. The PayPal rate-limit handling is thoughtful: it narrows the date window on retry and flags customers clearly if the API won't cooperate. Use it when someone asks "who owes me money" or you need to follow up on late payments without manually sorting through history and crafting different tones for different customers.

skills.sh installs: 2.1K
GitHub stars: 35.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add anthropics/knowledge-work-plugins --skill invoice-chase --agent claude-code

Installs into .claude/skills of the current project.

Files

Invoice Chase

Quick start

Pull the AR aging report, score each customer by payment history, draft a tone-matched reminder for each overdue invoice, and present them to the owner. Nothing sends until the owner says so.

User: "who owes me money"
→ Pull AR aging from the ledger
→ Cross-reference recent payments (PayPal 7-day window; other processors and the storefront 14 days; Airwallex paid status)
→ Score each customer: good-payer / occasionally-late / repeat-late
→ Draft tone-matched reminders
→ Show summary table + drafts. Wait for "send these."

Setup (first run only)

Ask the owner one question before running for the first time:

Mail connector: "Do you use Gmail or Microsoft 365 for drafts?" — store the answer; use it for all non-PayPal draft queuing. If only one mail connector is connected, use it and skip the question. Either way, confirm the mailbox is the owner's before queuing a draft in it (../../shared/tenant-scope.md).

Do not ask again on subsequent runs. Stripe is not a setup question: when it is connected, its overdue invoices are pulled every run (reference/v2_sources.md).