Agent skill

Collections Email

by mohitagw15856 in mohitagw15856/pm-claude-skills

Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices.

MITAuto-check passedDocuments & Office

Install Collections Email

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill collections-email -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills collections-email --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/collections-email .claude/skills/collections-email && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
collections-email
GitHub stars
1.4k
Token cost
~1.1k tokens
SKILL.md length
544 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices.

  • Works in 5 steps: Pre-due reminder (optional, ~3–5 days… → Due-date / just-overdue (day 0–3) —… → Overdue reminder (~7–14 days) — firmer,… → …
  • Asked to write a collections email
  • SKILL.md covers Working from a brief, Required Inputs, Output Format and Quality Checks, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Collections Email is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Forms and invoices and Email marketing. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked to write a collections email
  • A payment reminder
  • A dunning sequence
  • Chase an overdue invoice

Example prompts

  • “/collections-email”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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…
  5. Final notice (~30–45 days) — formal; state the next step if unpaid (pause work, escalate per terms) — factual, not threatening.

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Collections Email loads about 1.1k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 544 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~108
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 544 words, ~1,073 tokens.

Download SKILL.mdSave it as .claude/skills/collections-email/SKILL.md (or your agent's skills folder).
name
collections-email
description
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.

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.

Show full SKILL.md (181 more words)Show less

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

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/collections-email of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Collections Email next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Collections Email compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Collections Email this skillmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Paginated Reportdata-goblin/power-bi-agentic-development1k—~3.5kAutomated safety check: PassGPL-3.0
Browser Ops SkillOpenLoaf/OpenLoaf108—~1.5kAutomated safety check: PassAGPL-3.0
Extract Document Datasickn33/agentic-awesome-skills47k1 repos~1.1kAutomated safety check: PassApache-2.0
PDFzai-org/ZCode7.7k—~18kAutomated safety check: NotesProprietary
Form Fillingplatonai/Browser41.2k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Paginated Report

    data-goblin/power-bi-agentic-development

    Author, validate, publish, and test Power BI paginated reports in the RDL format.

    1k GitHub stars~3.5k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Browser Ops Skill

    OpenLoaf/OpenLoaf

    Triggered when the user asks for page-level interaction with a specific webpage: login, form filling, button clicks, pagination scraping, screenshots, downloading page images, handling CAPTCHAs or…

    108 GitHub stars~1.5k tokensUpdated 4 mo ago
    Documents & OfficeAuto-check passed
  • Extract Document Data

    sickn33/agentic-awesome-skills

    Extract structured, grounded fields from documents — values cite their page, missing values abstain instead of hallucinating.

    47k GitHub starsUsed in 1 repo~1.1k tokens
    Documents & OfficeAuto-check passed
  • PDF

    zai-org/ZCode

    Professional PDF toolkit covering four production workflows: reports, creative visuals, academic LaTeX, and existing PDF processing.

    7.7k GitHub stars~18k tokensUpdated yesterday
    Documents & OfficeAuto-check: notes
  • Form Filling

    platonai/Browser4

    Automatically fills web forms using provided field data and can optionally submit the form.

    1.2k GitHub stars~1.1k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Code2media

    tsingliuwin/autoclaw

    Universal media renderer with no fixed template — any custom layout, size or style becomes pixel-perfect images (PNG/JPEG/WebP), vector SVG, paged PDFs or animations (WebP/GIF).

    283 GitHub stars~985 tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Collections Email

What does Collections Email do?

Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices. Collections Email is an agent skill from mohitagw15856/pm-claude-skills. Write a polite-but-firm payment-reminder / collections email sequence for overdue invoices.

When should I use Collections Email?

Collections Email fits situations like: asked to write a collections email; A payment reminder; A dunning sequence; chase an overdue invoice.

How do I install Collections Email in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill collections-email -a claude-code`. Or copy the skill folder (skills/collections-email in mohitagw15856/pm-claude-skills) into .claude/skills/collections-email in your project. Claude Code loads it when a task matches its description.

How do I install Collections Email in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill collections-email -a codex`. Or copy the skill folder (skills/collections-email in mohitagw15856/pm-claude-skills) into .agents/skills/collections-email in your project. Codex loads it when a task matches its description.

Can I use Collections Email in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill collections-email -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/collections-email, .gemini/skills/collections-email, .github/skills/collections-email and .opencode/skills/collections-email in your project.

What does Collections Email need to run?

SKILL.md names no scripts, command-line tools or credentials: Collections Email is instructions for the agent only.

Does Collections Email access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Collections Email safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Collections Email use?

Collections Email is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Collections Email use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Collections Email?

Skills that share tags, products or a category with Collections Email: Paginated Report (data-goblin/power-bi-agentic-development, 1k stars), Browser Ops Skill (OpenLoaf/OpenLoaf, 108 stars), Extract Document Data (sickn33/agentic-awesome-skills, 47k stars) and PDF (zai-org/ZCode, 7.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Collections Email?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.