Agent skill · Content & Marketing

collections-email

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.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill collections-email --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/collections-email/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Collections Email Skill 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. ## Working from a brief 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. ## Required Inputs Ask for these only if they aren't already provided (else mark to insert): - **The invoice** — number, amount, original due date, and how overdue it is. - **The rel

What's inside
Steps it walks through
  1. Working from a brief
  2. Required Inputs
  3. Output Format
  4. Collections Sequence: [invoice]
  5. Quality Checks
  6. Anti-Patterns
  7. Based On
More from pm-claude-skills
All skills →
About this skill
What does the collections-email skill do?

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.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill collections-email --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going