What do I need to use Collections Email?

The invoice; The relationship; Terms; Payment method.

Is Collections Email free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Collections Email

Q: How do I know the Collections Email output is good?

The skill verifies itself against its own quality checks: The sequence escalates in firmness over a sensible cadence (gentle → formal final notice); Every email restates the amount, invoice number, and an easy way to pay; Early emails assume good faith (oversight), not bad intent; The final notice states a concrete, factual next step — not an empty or unlawful threat.

🔵 Stable🕐 updated 2026-06-30 🔷 SkillSpec L3 pm-accounting

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The invoice — number, amount, original due date, and how overdue it is.

▸The relationship — client name, contact, and whether they're a valued ongoing client or a one-off.

▸Terms — your payment terms and any agreed late-fee/interest (flag to confirm enforceability).

▸Payment method — exactly how they can pay (link, bank details), to remove friction.

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓The sequence escalates in firmness over a sensible cadence (gentle → formal final notice)

✓Every email restates the amount, invoice number, and an easy way to pay

✓Early emails assume good faith (oversight), not bad intent

✓The final notice states a concrete, factual next step — not an empty or unlawful threat

✓Tone stays professional throughout — firm, never abusive

✓Late-fee/interest and escalation are flagged to confirm, not asserted as enforceable

⚠️ What it refuses to do

Do not open with hostility — most late payments are oversight; start friendly

Do not make it hard to pay — repeat the payment link/details in every message

Do not threaten legal action or fees you can't or won't enforce — keep it factual and lawful

Do not wait until 60 days to send the first chase — a pre-due/just-due nudge gets paid fastest

Do not present this as legal advice — flag interest/escalation for professional confirmation

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="collections-email"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Collections Email is one of 599 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog