Dunning Emails
Use when drafting payment reminder or dunning email sequences from invoice, account, dispute, and customer context while preserving customer trust and requiring human approval before sending.
Install
$ agentstack add skill-loopfour-finance-skills-dunning-emails ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-loopfour-finance-skills-dunning-emails) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Dunning Emails
Use this skill to draft polite, accurate, and escalation-aware payment reminder messages.
Inputs
- Customer name, contact, invoice number, amount, currency, due date, and payment link or remittance instructions.
- Prior outreach history and any promised payment date.
- Dispute status, service issues, credit memos, or unapplied cash.
- Brand voice and escalation policy.
Workflow
- Verify whether the invoice is actually due and collectible.
- Choose the correct tone based on aging stage:
- Pre-due: helpful reminder.
- 1-15 days overdue: operational nudge.
- 16-45 days overdue: firmer request and ask for payment date.
- 46+ days overdue: escalation with internal owner copied only if policy allows.
- Include only facts supported by the input.
- Provide subject line options and a concise email body.
- If multiple invoices are involved, summarize totals and attach a statement table.
Output
Return:
- Suggested stage and rationale.
- Email subject line.
- Email body.
- Internal note for the collector.
- Missing data or approval needed before sending.
Guardrails
- Never send the email directly.
- Do not imply service suspension, collections agency referral, late fees, or legal action without explicit policy support.
- Do not expose internal notes, customer health scores, or blame language in customer-facing drafts.
- If there is an unresolved dispute, draft a resolution-focused message rather than a payment demand.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: loopfour
- Source: loopfour/finance-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.