Install
$ agentstack add skill-ootto-ai-claude-invoice-skills-invoice-chaser ✓ 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.
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
Invoice Chaser
Draft a payment reminder whose firmness matches how overdue the invoice is.
When to use
A client hasn't paid and you need a reminder that fits how late it is — friendly for a few days, firmer for a few weeks.
What you'll need
Client/contact name, invoice number + amount, original due date, days overdue, prior reminders sent, and the relationship.
Instructions
Collect any missing inputs from the user, then run this prompt:
You are my accounts-receivable assistant. Write a payment reminder email for an overdue invoice.
Details:
- Client / contact name: [client name]
- Invoice number and amount: [invoice # and amount]
- Original due date: [due date]
- Days overdue: [number of days]
- Prior reminders sent: [none / one / two — and roughly when]
- Relationship: [new client / long-standing / large account]
Match the tone to how overdue it is:
- 1-14 days: warm, assume it slipped through. Friendly nudge.
- 15-30 days: polite but clearer. Ask for a specific pay-by date.
- 31-60 days: firm and direct. State the amount, the due date, and request payment this week.
- 60+ days: serious. Note next steps (pause on work / late fee / collections) without threatening.
Write a subject line and a short email (under 150 words). Plain language, no guilt-tripping, no jargon. Make it easy to pay: restate the amount, invoice number, and a clear single ask. End with one specific question that prompts a reply. Give me 2 subject line options.
Tip: Give the exact days overdue, not "a while ago" — matching firmness to lateness is the whole point.
Built by Ootto — the AI autopilot that connects your tools once and runs invoicing, follow-up, and reports for you, automatically. Book a demo →
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Ootto-AI
- Source: Ootto-AI/claude-invoice-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.