Collections Email logo

Collections Email

CommunityPopular
mohitagw15856
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.

Overview

Publishermohitagw15856
Repositorypm-claude-skills
Skill namecollections-email
Stars
1.4K
Forks
257
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by mohitagw15856 on GitHub. Read the source before you install it.

Installation

Install the Collections Email AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-accounting/skills/collections-email
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p .claude/skills
cp -r /tmp/pm-claude-skills/plugins/pm-accounting/skills/collections-email .claude/skills/collections-email
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Collections Email in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Collections Email on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Collections Email is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 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.

Output Format

Collections Sequence: [invoice]

A staged set of emails, each short, professional, and with a clear pay-now path:

  1. Pre-due reminder (optional, ~3–5 days before) — friendly heads-up the invoice is due soon.
  2. Due-date / just-overdue (day 0–3) — assume an oversight; warm nudge, restate amount + due date + how to pay.
  3. Overdue reminder (~7–14 days) — firmer, still polite; note it's now overdue, ask for a payment date or to flag an issue.
  4. Second overdue (~21–30 days) — clear and direct; reference the terms, request immediate payment or a call, mention any agreed late fee (confirm).
  5. Final notice (~30–45 days) — formal; state the next step if unpaid (pause work, escalate per terms) — factual, not threatening.

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.

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
  • Tone stays professional throughout — firm, never abusive
  • Late-fee/interest and escalation are flagged to confirm, not asserted as enforceable

Anti-Patterns

  • 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

Based On

Accounts-receivable practice — staged dunning sequences that escalate professionally, remove payment friction, and preserve the client relationship.

Example Trigger Phrases

  • "Write a collections email."
  • "Chase an overdue invoice."
  • "Write a payment reminder."
  • "Set up a dunning sequence."

Frequently asked questions

What does the Collections Email AI 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.

Why use Collections Email on TypingMind?

Because you install it once and use it with any model. Collections Email is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Collections Email in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-accounting/skills/collections-email. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Collections Email?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Collections Email?

As many as you like. As long as a model supports skills, you can use Collections Email with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Collections Email AI skill free?

Yes. It is published on GitHub by mohitagw15856 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇