invoice-chase
Skill2 starsChanged 10 days agoMITView on GitHub
Review and chase overdue invoices — grouped by aging (30/60/90+ days), with total outstanding and option to send reminders.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- CSPulse/customer-success-skillstheir own version, first seen Nov 8, 2026
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- alebgl77/claude-inctheir own version, first seen Jul 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- anthropics/knowledge-work-plugins★ 35ksame name
- alebgl77/claude-inc★ 21same name
- CSPulse/customer-success-skills★ 2same name
- Big-LAORE/Biblioth-que-de-skills★ 1same name
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 repository4 other files it gives its agents.
- business-healthSkill
- competitor-intelSkill
- daily-briefingSkill
- prospect-researchSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Call invoice_list with status=overdue
- Very specific: line 11
Call finance_summary for context on total receivables
- Very specific: line 28
If yes, use invoice_send for each selected invoice.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chase Overdue Invoices
Review overdue invoices and help collect payment.
Steps
- Call
invoice_listwith status=overdue - Call
finance_summaryfor context on total receivables
Output Format
Group invoices by urgency:
OVERDUE INVOICES — EUR [total]
CRITICAL (90+ days) — EUR X
- #INV-001 | Customer | EUR 1,500 | Due: 2026-04-15
WARNING (60-90 days) — EUR Y
- #INV-002 | Customer | EUR 800 | Due: 2026-05-20
ATTENTION (30-60 days) — EUR Z
- #INV-003 | Customer | EUR 2,200 | Due: 2026-06-10
Then ask: "Want me to send reminders for any of these?"
If yes, use invoice_send for each selected invoice.
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.

