invoice-builder
Skill0 starsChanged 47 days agoMITView on GitHub
Build a new commercial invoice, proforma invoice, customs goods-value invoice or packing list XLSX from confirmed trade data. Use for document creation, not repricing or editing an existing customer workbook.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nawazxz/20-claude-skills-for-businesstheir own version, first seen Aug 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nawazxz/20-claude-skills-for-business★ 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 repository8 other files it gives its agents.
- freight-estimatorSkill
- landed-costSkill
- multi-quoteSkill
- quote-auditSkill
- supplier-rfqSkill
- translate-rfqSkill
- whatsapp-rfqSkill
- xlsx-editSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 8
Use scripts/build_invoice.py.
≈ “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
Trade documents
Use scripts/build_invoice.py; install openpyxl>=3.1.5,<4 if needed. It creates a new workbook and refuses to overwrite an existing file.
Choose the document
commercial: agreed goods prices, optional freight, total.proforma: a pre-sale document using prices and terms the user has explicitly supplied.customs: description, material, use, HS code and goods subtotal. No freight or combined total. Do not infer HS codes, suppress a required trademark, or alter declared values to evade duties.packing: quantities, carton count, net/gross weight and volume. No prices. Missing measurements stay blank.
Inputs and execution
Confirm seller, buyer, document number, date, currency and line items. Do not invent contacts, prices, measurements or delivery promises. Use the repository's examples/invoice.json (commercial, proforma and customs) or examples/packing.json as schema examples; all their contents are fictional.
python scripts/build_invoice.py input.json --kind commercial --output Commercial_Invoice_DEMO.xlsxRun relative to this skill folder, or substitute the absolute script path. Each item needs description and positive quantity; invoices also need unit_price. Commercial/proforma items optionally carry part_no, model, unit; customs items carry material, use, hs_code. Packing items optionally carry part_no, unit, cartons, net_kg, gross_kg, cbm.
The script uses two-decimal unit prices and amounts with half-up rounding, then sums the visible line amounts. It rejects unsupported fields, including internal cost/margin/supplier fields, and stores user text as text rather than formulas.
Check the result
Reopen the generated XLSX. Reconcile descriptions, quantities, visible prices, subtotal and total with the supplied data. Inspect the print layout for long descriptions or addresses. Check customs files have only a goods subtotal, and packing lists contain no prices. Generating a file does not authorize sending it or filing a declaration.
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.

