Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices. Use when asked to write a collections email, a payment reminder, a dunning sequence, or to chase an overdue invoice. Produces a staged sequence — gentle pre-due nudge through escalating overdue reminders to a final notice — that stays professional, keeps the relationship intact, and makes paying easy. Not legal advice.
.claude/skills/mohitagw15856-collections-email/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 29% | 0% |
| case-02 | ✗→✓ | ▲ Improved | 46% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 27% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 132% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 22% | 0% |
Chasing payment is uncomfortable, so it's often done too late or too harshly. The effective approach is a staged sequence that starts friendly and firms up on a schedule — always professional, always making it trivially easy to pay. This skill writes that sequence so you get paid without burning the relationship.
> Note: this is a communication aid, not legal or debt-collection advice. Late-payment interest, > statutory rights, and regulated debt-collection rules vary by jurisdiction — confirm any interest/late fees > and escalation (collections agency, legal) with an accountant/lawyer before acting on them.
Given "chase a client whose $5,000 invoice is 2 weeks overdue", write the full sequence anyway — infer a sensible cadence and tone progression, marking specifics (insert invoice #, amount, dates, payment link). Don't state late-fee/interest amounts as enforceable — flag them to confirm. Never threaten beyond what's lawful/intended.
Ask for these only if they aren't already provided (else mark to insert):
A staged set of emails, each short, professional, and with a clear pay-now path:
For each: a subject line, a short body, and the payment details/link repeated. Tone firms up across the sequence but never becomes abusive.
Add notes: insert real invoice details; confirm any interest/late fee and escalation are lawful and intended.
Accounts-receivable practice — staged dunning sequences that escalate professionally, remove payment friction, and preserve the client relationship.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-18 | pass→pass | 14,120 | 13,369 | -5% | 1 | 1 | 0% | 2,729 | 3,494 | +28% | 0 | 0 | — |
case-01 | fail→pass | 13,982 | 13,331 | -5% | 1 | 1 | 0% | 2,807 | 3,626 | +29% | 0 | 0 | — |
case-02 | fail→pass | 15,169 | 16,659 | +10% | 1 | 1 | 0% | 2,858 | 4,185 | +46% | 0 | 0 | — |
case-03 | fail→pass | 17,415 | 15,147 | -13% | 1 | 1 | 0% | 3,141 | 4,000 | +27% | 0 | 0 | — |
case-04 | pass→pass | 10,066 | 9,824 | -2% | 1 | 1 | 0% | 1,929 | 2,642 | +37% | 0 | 0 | — |
case-05 | pass→pass | 11,009 | 11,556 | +5% | 1 | 1 | 0% | 2,417 | 3,285 | +36% | 0 | 0 | — |
case-06 | pass→pass | 9,496 | 10,299 | +8% | 1 | 1 | 0% | 2,022 | 2,782 | +38% | 0 | 0 | — |
case-07 | fail→fail | 6,371 | 6,985 | +10% | 1 | 1 | 0% | 1,189 | 2,192 | +84% | 0 | 0 | — |
case-19 | pass→pass | 7,480 | 8,374 | +12% | 1 | 1 | 0% | 1,380 | 2,321 | +68% | 0 | 0 | — |
case-08 | fail→pass | 8,083 | 10,591 | +31% | 1 | 1 | 0% | 1,267 | 2,942 | +132% | 0 | 0 | — |
case-09 | fail→fail | 10,771 | 10,257 | -5% | 1 | 1 | 0% | 1,865 | 2,600 | +39% | 0 | 0 | — |
case-10 | pass→pass | 12,383 | 10,388 | -16% | 1 | 1 | 0% | 2,124 | 2,958 | +39% | 0 | 0 | — |
case-11 | pass→pass | 7,103 | 8,939 | +26% | 1 | 1 | 0% | 1,342 | 2,510 | +87% | 0 | 0 | — |
case-12 | pass→pass | 11,154 | 10,889 | -2% | 1 | 1 | 0% | 2,182 | 2,935 | +35% | 0 | 0 | — |
case-13 | pass→pass | 10,029 | 7,629 | -24% | 1 | 1 | 0% | 1,724 | 2,261 | +31% | 0 | 0 | — |
case-14 | pass→pass | 11,735 | 10,639 | -9% | 1 | 1 | 0% | 2,065 | 2,840 | +38% | 0 | 0 | — |
case-15 | fail→pass | 12,724 | 10,383 | -18% | 1 | 1 | 0% | 2,363 | 2,894 | +22% | 0 | 0 | — |
case-16 | pass→pass | 10,110 | 11,257 | +11% | 1 | 1 | 0% | 1,809 | 3,171 | +75% | 0 | 0 | — |
case-17 | pass→pass | 8,466 | 9,401 | +11% | 1 | 1 | 0% | 1,372 | 2,405 | +75% | 0 | 0 | — |
case-20 | pass→pass | 11,772 | 10,711 | -9% | 1 | 1 | 0% | 2,276 | 2,881 | +27% | 0 | 0 | — |
case-21 | fail→pass | 10,926 | 8,822 | -19% | 1 | 1 | 0% | 2,014 | 2,549 | +27% | 0 | 0 | — |
case-22 | pass→pass | 6,732 | 6,069 | -10% | 1 | 1 | 0% | 1,282 | 1,895 | +48% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +27 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.