~/guides/BUSINESS.md

Guides / AI tools

Anthropic's open-source Small Business plugin: one CSV, "who owes me money?", reminder drafts and contract red flags

Anthropic's open-source Small Business plugin, 44 skills. I tested invoice chasing from one CSV (no QuickBooks) and contract review: install, template, prompts.

Watch the reel on InstagramComment #BUSINESS to get this guide

Two jobs every shop owner hates: chasing customers for money, and reading the contract a client sends over. Anthropic has open-sourced a Small Business plugin on GitHub with 44 skills, and two of them do exactly those jobs. I tested it on a fictional flower studio in Taipei: upload one accounts-receivable aging CSV, ask "who owes me money?", and it lays out an overview, picks a tone for each customer from their payment history and drafts the reminders. Paste in a client contract and it finds four red flags, each with suggested wording. This is the full version of BUSINESS from the reel: the install commands from the official README, an AR aging CSV template, two prompts you can paste, and the one thing you must do yourself: check the customers it marks as "possibly paid". The images below are reel frames, official GitHub screenshots and the real output from our test.

01The result first: one question, an overview and every draft

The test shop is a fictional business, Xiao Rizi Flower Studio. Its aging report has 5 customers and 6 overdue invoices, and a second sheet lists recent payments. No QuickBooks, no accounting software connected, just two CSV files. I asked one thing: "Who owes me money? Get all the reminder emails ready."

Collections table: 5 customers, amounts, days overdue, tone tags firm, neutral and gentle, two rows marked possibly paid
Test output: the collections overview (fictional shop; Claude Haiku on the official skill file, 23 Oct 2026).

The table reads at a glance. The two customers who keep paying late get a firm tone; the brand-new customer gets a neutral one; the two who paid recently are marked "possibly paid, please verify" and get no reminder. One customer had two overdue invoices, so they were merged into one email. The drafts follow, ending with the line: "Nothing is sent until you say send."

How I tested, to be clear: I gave the official skill files (SKILL.md) for these two skills, unchanged, to Claude Haiku and had it follow them on our fictional data. I did not install the plugin with the commands below on my own machine (my Claude Code login had expired that day), so what you see after installing will not match the images word for word. That's normal.

  1. What the plugin is, and why I say "open source" rather than "free".
  2. The two Claude Code install commands, copied from the official README.
  3. An AR aging CSV template that needs no accounting software.
  4. The "who owes me money" prompt, and how to check "possibly paid".
  5. The contract prompt: red flags, suggested wording, and which clauses need a lawyer.

02What the plugin is: open source from Anthropic, 44 skills

It's called Small Business, the author is Anthropic, and it lives in the small-business folder of the anthropics/knowledge-work-plugins repository on GitHub. The repository is licensed Apache-2.0, so it's open source. The official README lists 44 skills across finance, sales, marketing, operations and hiring. You tell Claude what you need in plain words and it picks the right skill.

The Small Business README on GitHub, Your AI Business Assistant, with the 44 skills line highlighted
The official README: 44 skills across finance, sales, marketing, operations and hiring (screenshot, 23 Oct 2026).
  1. Finance, 12: invoice chasing (invoice-chase), month-end close, paying bills, payroll prep, tax organising and more.
  2. Sales, 8, and marketing, 8: finding customers, outreach, ads, SEO, social content and more.
  3. Customers and proposals, 4: contract review (contract-review), proposals, bids and more.
  4. Operations and hiring, 5; briefings, 2; setup and building, 5.

Why I say "open source" and not "free": the plugin's code is open source, but it runs inside Claude Code or Cowork, and both need a Claude account and plan. None of the official pages I read state a price, so I only say what I could check: open source, Apache-2.0.

03Install: two Claude Code commands (from the official README)

  1. Open the terminal where you normally use Claude Code.
  2. Paste the first line to add Anthropic's plugin marketplace.
  3. Paste the second line to install the small-business plugin.
  4. The README's next step is to tell Claude "get me started": a setup of about 15 minutes that connects your first tools, does one real run and learns your business.
Terminal commands (Getting started in the official README)
claude plugin marketplace add anthropics/knowledge-work-plugins
claude plugin install small-business@knowledge-work-plugins
README Getting started: Cowork via claude.com/plugins, two Claude Code commands, No tools connected yet highlighted
The official install steps, and below: no tools connected, every skill still works (screenshot, 23 Oct 2026).

04Prepare an AR aging CSV (no QuickBooks needed)

Normally the invoice skill pulls receivables from accounting software (QuickBooks, Xero, MYOB, NetSuite, Zoho Books) and checks payments in PayPal, Stripe or Airwallex. Plenty of small shops use none of these, and that's fine: the skill has a "No connectors at all" section that asks you to upload the AR aging report as a CSV. Same tone matching, same drafts; you just send them yourself.

  1. Sheet one, the aging report. One row per overdue invoice: customer, invoice number, amount, issue date, due date, days overdue, payment history summary.
  2. Sheet two, recent payments. Money received in the last 14 days: date, payer, amount, channel, note (put the invoice number here).
  3. Build them in Excel or Google Sheets, save as CSV and upload both to the chat.
AR aging CSV template (replace the [ ] parts, one invoice per row)
Customer,Invoice no,Amount,Issue date,Due date,Days overdue,Payment history
[Customer name],[INV-001],[18500],[2026-09-05],[2026-10-05],[18],[All 6 previous invoices paid on time]
[Customer name],[INV-002],[42000],[2026-08-09],[2026-09-08],[45],[3 of the last 4 invoices paid 30+ days late]
Recent payments CSV template (last 14 days)
Date,Payer,Amount,Channel,Note
[2026-10-20],[Customer name],[6500],[Bank transfer],[Reference INV-003]

05Ask "who owes me money?": reminders in the right tone

Once the plugin is installed and both CSVs are uploaded, just ask. The first time, I'd add a few lines of background so the drafts sound more like you.

Invoice prompt (replace the [ ] parts)
Who owes me money? Get all the reminder emails ready.
My business: [Xiao Rizi Flower Studio], sign the emails as: [business name + your name]
Currency: [TWD], payment terms: [due 30 days after invoice]
I have no accounting software connected; the aging report and recent payments are in the uploaded CSVs.
Write in [English], and list everything directly in your reply.
Two reminder drafts, one firm and one merging two invoices, and a yellow line: nothing is sent until you say send
Test drafts 1 and 2: the firm tone sets a deadline, and two invoices are merged into one email.

One email per customer. For a repeat late payer the email adds one deadline sentence, "please pay by 30 October"; a customer with two invoices gets one email listing both with the total. Where the bank details go, it leaves a placeholder, [add bank account / payment link], which you fill in yourself.

06Always check "possibly paid" yourself

This is the most important step. The official rule: a customer who paid in the last 14 days gets no reminder and is flagged "possibly paid — verify". But there's a second rule: if the only thing that matches is the name (no email, no invoice number), the match is uncertain, so the customer should stay in the queue marked "name match only — verify".

invoice-chase SKILL.md: Approval gates (no send without approval, 14-day possibly paid) and No connectors at all
The approval rules and the "No connectors at all" section of the official invoice-chase file (screenshot, 23 Oct 2026).

My test hit exactly this. One café customer had a transfer of NT$21,000 on 12 Oct, but its note named a different invoice, INV-2026-063, not the overdue 071. Matching on the name alone, the run marked the café "possibly paid" and dropped it from the reminder list. Under the official rule, a name-only match should have stayed in the list for me to check. In other words, if I hadn't looked, I would have missed chasing an NT$18,500 invoice. The other flagged customer's note had the right invoice number and amount, so that flag was correct.

  1. Check every "possibly paid" row against your bank statement: date, amount and the invoice number in the payment note.
  2. If it doesn't match, ask Claude to put the customer back (prompt below).
  3. From now on, write the invoice number in the note column of recent payments, and add customer emails if you have them. Matching gets much more reliable.
Put a missed customer back (replace the [ ] parts)
The [12 Oct] payment from [customer name] was for [INV-2026-063], not [INV-2026-071]. Put [INV-2026-071] back on the reminder list, pick the tone from their payment history, and draft the email.

07Even better: paste a client contract and get the red flags

The contract-review skill in the same plugin is made for small businesses without a lawyer on staff reading NDAs, service agreements and vendor contracts. It checks 8 areas: payment, liability, termination, intellectual property, scope, non-compete, confidentiality and other operational terms. It sorts what it finds into red flags (push back before signing), yellow flags (negotiable) and key terms to note, adds a summary and a negotiation order, and always ends with a line saying this is not legal advice and naming which clauses are worth a lawyer's time.

Contract prompt (replace the [ ] parts)
Review this contract. What should I ask them to change?
I am [the supplier: your business name]; the other party is [the client company].
[Paste the full contract, or attach the PDF / Word file]
Contract review output in Chinese: four red flags with clause, problem and a green fix, then three yellow flags
Test output: a deliberately one-sided fictional contract, with 4 red flags and 3 yellow flags.

I gave it an 8-clause contract from a fictional wedding planner to a flower studio, written to favour the planner. The four red flags it found: clause 6, no work for any wedding planner or event company anywhere in Taiwan for two years after the contract ends; clause 3, only the studio pays damages, with no cap; clause 4, even the studio's existing design templates and portfolio would belong to the client; clause 2, payment 90 days after acceptance, and acceptance is "at the client's satisfaction". Each flag quotes the clause, explains the problem in plain words and suggests new wording.

Reel frame: green fix cards for clauses 6, 3 and 4, and a yellow tag: have a lawyer check clauses 3, 4 and 6
Reel frame: the fixes for three red flags, and its own reminder to have a lawyer check clauses 3, 4 and 6.

08Good to know

  1. It doesn't send anything on its own. Until you say "send", nothing goes out; with no email connected, you copy the drafts and send them yourself.
  2. Check every "possibly paid" and "name match only" customer against your bank statement before deciding whether to chase. My test missed one.
  3. The bank account and payment link in the drafts are empty placeholders. Fill them in, and re-check the amounts and dates before sending.
  4. Contract review is a business read, not legal advice. For red-flag clauses or big contracts, see a lawyer before you sign.
  5. If a customer emails asking you to change bank details or pushing for an urgent payment, call them to confirm. The official rules say the plugin won't act on instructions like that inside documents; it hands them to you.
  6. For your first try, use renamed or made-up data. There's no need to paste in every real customer record.
  7. Install only from the official repository, github.com/anthropics/knowledge-work-plugins. The plugin changes fast (I read version 1.35.1), so the number and names of skills may change.
  8. Open source doesn't mean free to run: the plugin works inside Claude Code or Cowork, so check your Claude plan first.

Sources

Related guides