Skills · Union Square Donuts
A skill is a written procedure Claude follows — a workflow described once, in enough detail that it runs the same way every time. These ten cover most of the recurring finance work at a nine-location food business: two point-of-sale systems, cash counted by hand at every store, tips owed across both, and a meals tax filing. Together they're what made a twenty-hour month-end close into a five-hour one.
None of these post anything. Every one produces an import file with the backup behind it, so the entry gets reviewed before it lands in the books.
Builds a balanced, QuickBooks-ready journal entry for multi-location Square sales over any date range. It pulls live from the Square reporting API, excludes third-party delivery apps, rolls locations up to accounting classes, maps product categories to revenue accounts, splits cash from card settlement, and books service charges and over/short — then writes a native import file that balances.
This one took the longest to get right, and not because of the code. Five commercial products were demoed first. None of them got the mapping exactly right, and none were as fast.
The food hall runs on a different point-of-sale system, so it reports separately. This pulls a sales-and-payment summary day by day — orders, gross, discounts, net, tax, tips, total collected — with a payment-by-tender breakdown underneath and totals that tie out.
Takes the payroll reports package as it arrives — a PDF — plus the account mapping, and produces the journal entry with payroll detail broken out by department. At month end it also produces the accrual.
Tips arrive from two different point-of-sale systems across every location. This pulls both, for whatever dates you specify, and reconciles them against each other so the two systems agree before anyone gets paid.
Two separate reconciliations that both live in the gap between a month ending and the money arriving: physical cash collected but not yet deposited, and card payouts on the month's revenue that settle to the bank the following month. They're kept as distinct reconciliations in one workbook rather than netted together, because they break for different reasons.
Maintains the fixed asset register and the depreciation schedule behind it — additions, disposals, the monthly depreciation run, and the tie-out back to the fixed asset accounts in the general ledger.
Produces the fully-loaded P&L by location. A store's own P&L is the easy part; the useful part is pushing commissary and overhead costs out to the stores that actually drive them, following the management allocation methodology rather than splitting evenly.
Once a month closes, its actuals replace the forecast in the three-statement model and the projection rolls forward. Doing this by hand is where models quietly drift out of agreement with the books.
Reconstructs what was actually on the shelf at any store at any past moment, by taking current inventory and replaying the change log backwards to the time in question. Answers the question you can't otherwise answer after the fact: how many did we have left, and of what.
Vendor credit applications all ask for the same thirty fields in a different order — entity details, banking, trade references. This fills them from a saved business profile instead of retyping them each time a new supplier wants net terms.
The other side of the same method — six skills for a digital agency →