invoice-builder
Skill0 starsChanged 3 months agoMITView on GitHub
Build a clean, professional invoice from line items. Use when someone lists what they did, quantities, and rates and needs it formatted as an invoice with totals and payment details.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jordan-partstrade/trade-agent-skillstheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jordan-partstrade/trade-agent-skills★ 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.
In this repository19 other files it gives its agents.
- ad-copySkill
- blog-writerSkill
- cold-outreachSkill
- content-repurposerSkill
- contract-summarizerSkill
- crm-note-cleanerSkill
- data-cleanerSkill
- expense-summarySkill
- faq-builderSkill
- follow-up-emailSkill
- lead-qualifierSkill
- meeting-notesSkill
- newsletter-writerSkill
- proposal-writerSkill
- review-responderSkill
- social-post-packSkill
- sop-writerSkill
- support-replySkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If tax or currency is unstated, ask rather than assuming.
- Distinctive: line 21
Add payment instructions and terms (e.g.
- Distinctive: line 29
Never invent a tax rate or bank detail.
- Distinctive: line 30
Keep it simple and professional.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Invoice Builder
Line items in, a correct, professional invoice out.
Inputs needed
- The line items: description, quantity, and rate for each.
- Sender and client details (name, address/email).
- (Optional) Tax rate, currency, due date, invoice number, payment method.
If tax or currency is unstated, ask rather than assuming.
Steps
- Lay out header details: from, to, invoice number, issue date, due date.
- List each line item with description, quantity, unit price, and line total.
- Sum the subtotal, apply tax if given, show the grand total.
- Add payment instructions and terms (e.g. due in 14 days).
- Double-check the math before presenting.
Output format
A clean invoice with header, an itemized table, subtotal / tax / total, and a payment section. Offer it as Markdown and note it can be rendered to PDF.
Voice & rules
- Get the arithmetic right. Re-add the totals before showing them.
- Never invent a tax rate or bank detail; flag anything missing.
- Keep it simple and professional.
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.

