Invoice chaser

Skill thefiredev-cloud/meshvault-skills-starter/skills/invoice-chaser

Free open agent skills from MeshVault. Plain Markdown, approval-gated, MIT. Private AI staff on hardware you own.

Install

npx -y skills add thefiredev-cloud/meshvault-skills-starter --skill invoice-chaser

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

This skill should be used when the user asks to "chase invoices", "who still owes us", "send payment reminders", or wants overdue receivables nudged politely without anything sending before approval.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 406 tokens by cl100k_base, as published. Nobody here has run it

Invoice Chaser

Find overdue invoices, draft a friendly reminder for each one in the owner's voice, and stop at the approval gate. Nothing sends until the owner says yes.

Required Inputs

The invoice list (a spreadsheet, an accounting export, or a plain Markdown table with client, amount, due date, and status)
Client contact emails
The owner's preferred tone, if one is on file (default: warm, brief, zero pressure on the first nudge)

Steps

Read the invoice list. Select every invoice past its due date that is not marked paid or disputed.
Sort by days overdue, largest amount first inside each bucket.
For each overdue invoice, draft one reminder email:
- First nudge (1 to 14 days late): friendly, assume it slipped their mind, restate amount and due date, offer the payment link.
- Second nudge (15 to 30 days late): direct, restate terms, ask for a payment date.
- Third nudge (31+ days late): flag to the owner instead of drafting. Late accounts at this stage need a human decision, not another template.
Stop. Present every draft to the owner with client, amount, days late, and the full email body.
Only after explicit approval, send the approved drafts. Never send a reminder the owner has not seen.
Log what was sent, to whom, and when, in decision-log.md or the system of record.

Approval Gate

Sending email to a client is a real-world action. This skill never sends on its own. If the owner approves some drafts and not others, send only the approved ones. If anything about an invoice looks disputed or already paid, hold it and ask.

Output

Sent reminders (after approval only)
A short summary: how many chased, how many held, total amount outstanding
A log entry per sent email