invoice-followup
Skill0 starsChanged 27 days agoMITView on GitHub
Draft payment reminder emails for unpaid invoices, escalating by how overdue they are. Use when the user mentions an unpaid, late, or overdue invoice, or asks how to chase a payment.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- runbooklabhq/freelancer-ops-skills-liteword for word, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- runbooklabhq/freelancer-ops-skills-lite★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- proposal-writerSkill
- scope-guardSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write the right reminder for how late the invoice is.
- Distinctive: line 17
If the user gives only "client X hasn't paid", ask for amount and due date — nothing else is required.
- Distinctive: line 38
Never apologize for asking.
- Distinctive: line 47
If stage ≥ Firm: a 2-bullet note on what to prepare (contract clause, record of delivery) in case it escalates.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Invoice Follow-up
Write the right reminder for how late the invoice is. Tone escalates with time; the relationship is preserved until the last stage.
Inputs to collect
- Invoice number, amount, original due date, today's date
- Client contact name and whether there's an accounts-payable contact
- Any prior reminders already sent
- Payment terms / late-fee clause in the contract (if the user has one)
If the user gives only "client X hasn't paid", ask for amount and due date — nothing else is required.
Escalation ladder
Pick the stage from days overdue. Never skip stages unless the user asks.
| Days overdue | Stage | Tone | Length |
| −3 to 0 | Courtesy heads-up | Friendly, assumes it's in progress | 3 sentences |
| 1–7 | Reminder | Warm, factual, offers help | 4–5 sentences |
| 8–21 | Firm | Direct, states consequence (work pause), asks for a date | 5–6 sentences |
| 22–45 | Final notice | Formal, references terms, sets a hard deadline, late fee if contract allows | 6–8 sentences |
| 45+ | Pre-collections | Formal, states next action (collections / legal / platform dispute), no pleasantries | Short |
Rules for every stage
- Subject line contains invoice number and amount:
Invoice #1042 — €1,200 — [stage word] - First sentence states the fact (invoice, amount, due date). No "hope you're well" after stage 1.
- One clear ask with a date: "Can you confirm payment by Thursday 23 Oct?"
- Re-attach or re-link the invoice every time; assume it was lost.
- Offer the easiest payment path (link, IBAN) in the body.
- Never apologize for asking. Never threaten anything the user won't do.
- At Firm stage and later: pause-of-work sentence is mandatory — "I'll hold the remaining deliverables until this is settled."
- Late fees only if the contract has a clause; otherwise don't mention them.
Output
Return:
- The email (subject + body), ready to send.
- A one-line next check — the date to follow up again and which stage comes next.
- If stage ≥ Firm: a 2-bullet note on what to prepare (contract clause, record of delivery) in case it escalates.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.