invoice
Skill0 starsChanged 8 months agoMITView on GitHub
Create and send invoices. Use when the user wants to invoice a client, create a bill, or send a factura.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- RiggdAI/invoicerigtheir own version, first seen Oct 20, 2026
- dithiothreitol/jdg-ksiegowytheir own version, first seen Oct 17, 2026
- metadist/synaplan-desktoptheir own version, first seen Sep 26, 2026
- AlpacaLabsLLC/skills-for-architectstheir own version, first seen Sep 20, 2026
- jpoindexter/theft-kittheir own version, first seen May 20, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- AlpacaLabsLLC/skills-for-architects★ 390same name
- metadist/synaplan-desktop★ 257same name
- dithiothreitol/jdg-ksiegowy★ 11same name
- jpoindexter/theft-kit★ 1same name
- RiggdAI/invoicerig★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Ask for the minimum information needed:
- Very specific: line 13
Use list_clients first to check if the client already exists.
- Distinctive: line 15
After creating the invoice, offer to:
- Distinctive: line 20
Keep it conversational. The user should be able to say "$ARGUMENTS" and get an invoice created with minimal back-and-forth.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Help the user create an invoice using the create_invoice tool.
Ask for the minimum information needed:
- Client name (or company) — if the client already exists, use their ID
- Amount or line items (description + amount for each)
- Currency (default to the user's profile currency)
Use list_clients first to check if the client already exists. If not, create_invoice will create the client automatically.
After creating the invoice, offer to:
- Send it by email with
send_invoice - Download the PDF with
download_pdf - Duplicate it later with
duplicate_invoice
Keep it conversational. The user should be able to say "$ARGUMENTS" and get an invoice created with minimal back-and-forth.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

