本文へ移動
cccskills
無料GitHub で公開

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.2 KB

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

日本語の概要は準備中です。原文の説明を表示しています。

mohitagw15856/pm-claude-skills1,4412026年10月13日 更新

mohitagw15856 のスキルをすべて見る

このスキルの問題を報告する