Invoice follow-up
List overdue invoices by age and amount, and draft a reminder for each customer in a tone that fits how late it is. Sends nothing and promises nothing.
In Lobstack: Skills › Library › Add
What your agent will do.
Invoices are past due — in Stripe, an accounting export or a spreadsheet — and someone needs to know who owes what, with the reminders ready to approve.
- 01
List every open invoice past its due date: customer, number, amount, due date, days late. Check for payments received but not yet matched before calling anything overdue.
- 02
Group by age — 1-14 days, 15-30, 31-60, over 60 — and total each group in a bar chart in a chart fence.
- 03
Read each customer's history: earlier reminders, disputes, promises to pay, notes from whoever owns the account. A disputed invoice needs a person, not a reminder.
- 04
Draft one reminder per customer covering all their late invoices. Early: friendly, assume it was missed, link the invoice. Later: firmer, ask for a payment date. Over 60 days: plain and direct, and flagged for a person. Never threaten, and never mention collection agencies or legal action.
- 05
Never offer a discount, payment plan, waived fee or new deadline. Write "needs approval" instead.
- 06
Post a document: the table by age, then the drafts, then what needs a person.
- 07
Send nothing. Each reminder goes out only once a person has approved it.
Check every amount and invoice number against the source. A reminder for a paid invoice costs more goodwill than it recovers.
The whole SKILL.md: 35 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: invoice-follow-updescription: "List overdue invoices by age and amount, and draft a reminder for each customer in a tone that fits how late it is. Sends nothing and promises nothing."metadata: title: "Invoice follow-up" category: finance tags: [finance, invoices]--- ## When to use this Invoices are past due -- in Stripe, an accounting export or a spreadsheet -- andsomeone needs to know who owes what, with the reminders ready to approve. ## How 1. List every open invoice past its due date: customer, number, amount, due date, days late. Check for payments received but not yet matched before calling anything overdue.2. Group by age -- 1-14 days, 15-30, 31-60, over 60 -- and total each group in a bar chart in a chart fence.3. Read each customer's history: earlier reminders, disputes, promises to pay, notes from whoever owns the account. A disputed invoice needs a person, not a reminder.4. Draft one reminder per customer covering all their late invoices. Early: friendly, assume it was missed, link the invoice. Later: firmer, ask for a payment date. Over 60 days: plain and direct, and flagged for a person. Never threaten, and never mention collection agencies or legal action.5. Never offer a discount, payment plan, waived fee or new deadline. Write "needs approval" instead.6. Post a document: the table by age, then the drafts, then what needs a person.7. Send nothing. Each reminder goes out only once a person has approved it. Check every amount and invoice number against the source. A reminder for a paidinvoice costs more goodwill than it recovers.
- Finance
Revenue snapshot
Summarise revenue for a period (new, expansion, churn, refunds, failed payments) against the last period, with a chart. Read-only.
SKILL.md · App - Finance
Spend review
Review a card or bank export: categorise every line, flag duplicates, new subscriptions and price rises, and total spend against last month.
SKILL.md · App - Finance
Payouts against the bank
Match a period's Stripe payouts against the bank feed line by line, and list what does not match — a missing deposit, a duplicate charge, a fee that moved — with the refund or fix left for a person.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App