Invoice Creator

A clean invoice gets paid faster than a messy one. The maths is right, the line items describe the work clearly, the payment method is explicit, and the due date is a specific date rather than a vague "Net 30". This skill produces invoices that hit all of those without you having to think about formatting. It asks the essentials first (who you're billing, what you did, how much, when it's due) and only chases the rest if it's not already in the profile — business name, contact details, invoice number system, currency, tax requirements, payment method.

Line items are structured by work type. Hourly work gets a description-hours-rate-amount table. Project-based work gets a description-quantity-unit-price table. Retainers get a description-period-rate table with the scope summary inline. Descriptions are specific enough that the client knows exactly what they're paying for but not so detailed they read like a justification of the price. For long projects, milestone or phase numbering is included so the client can match the invoice to the contract or proposal.

The maths is shown explicitly. After generating the invoice, the skill prints the full calculation — every multiplication, the subtotal, the tax line with rate, the total — so any error is caught at glance rather than after the client sends it back. A maths error on an invoice is a credibility cost; this prevents it. Tax compliance, though, stays your responsibility — the skill includes VAT and tax fields but flags that rates and registration requirements need verifying with an accountant.

Payment details are mandatory on every invoice — bank details for transfer, PayPal email or Stripe link, the specific due date, and a late-payment policy if you have one. For UK sole traders the 8% + Bank of England base rate is suggested as a defensible statutory default. You also get an invoice numbering system if you don't have one (sequential, date-based, or client-coded), and optional Day-7 and Day-30 reminder drafts in escalating tones — friendly forgot-it nudge, firmer payment-date request, formal final notice with late-fee reference. If the user describes the pricing vaguely ("around £5K", "roughly 40 hours") the skill flags it before generating — invoice disputes almost always start with unclear scope, and getting the number nailed in writing first is cheaper than chasing payment later.