An agent skill for expense tracking turns a pile of receipt photos into a clean monthly report. You photograph each receipt, the skill reads the vendor, date and total, sorts each item into your categories, and builds a report you review before anything reaches your books. Here is how to build one in Claude in an afternoon, with no code.
What the skill does (and what it does not)
An agent skill is a folder of instructions, scripts and resources that an agent loads when a task matches it. Anthropic describes Agent Skills as reusable, filesystem-based resources that give Claude domain-specific expertise, and each skill starts with a SKILL.md file whose name and description tell Claude when to use it. For expenses, that folder holds your category list, your rules for tricky receipts, and the template for your monthly report.
What it does not do: it does not replace your accountant, approve spending on its own, or move money or post to your accounting software without a human check. It prepares the paperwork; you stay the approver.
Before you start
Gather four things first: your category list (the 6 to 10 categories you actually use, such as Meals, Travel, Software and Supplies); one receipt inbox, a single shared folder or phone album where every receipt lands; one owner, who reviews the monthly report and fixes wrong categories; and a test set of five or six old receipts to test before it touches live expenses.
Step 1: Decide your categories and rules
Write each category with one example and one rule for ambiguous cases — most expense mistakes come from the grey area, not the obvious cases.
| Category | Example | Rule |
|---|---|---|
| Meals | Client lunch | Business meals only; personal meals excluded |
| Travel | Fuel, parking, tolls | Keep the trip purpose in the note |
| Software | Monthly subscriptions | One line per subscription, never bundled |
| Supplies | Printer paper, packaging | Receipts under $25 need no extra note |
| Misc | Anything that fits nowhere else | Always needs a one-line explanation |
Add one catch-all rule: if the skill cannot read a receipt clearly, or cannot pick a category with confidence, it must flag the item instead of guessing. A flagged receipt takes ten seconds to fix; a silently wrong category can sit in your books for months.
Step 2: Write the SKILL.md file
Create one folder for the skill and add a SKILL.md file inside it. The file starts with YAML frontmatter holding a name and a description. The description is what Claude matches your request against, so it must say both what the skill does and when to use it.
For example: “Reads receipt photos and turns them into a categorised monthly expense report for a small business. Use when the user uploads a receipt photo or asks for the monthly expense report.” Below the frontmatter, write the workflow in short numbered steps: read the vendor, date and total from the photo; match the vendor to a category; ask for the trip purpose or project name when the category needs it; add the item to the monthly report; flag anything unclear instead of guessing.
Skills use progressive disclosure: only the short name and description load into context at startup, at roughly 100 tokens per skill, and the full instructions load only when the skill triggers.
Step 3: Set up the receipt inbox
Pick one inbox and stick to it. A shared folder works well for a team: each person photographs a receipt the day they spend and drops it in with the date in the file name.
Tell the skill where the inbox lives and what a finished item looks like: vendor, date, total, category, and a one-line note where your rules require one. Photograph the whole receipt, flat, in good light — blurry, cropped photos are the most common reason a skill misreads a total.
Step 4: Teach it your approval rules
A skill that files expenses is useful; a skill that files expenses with your rules is trustworthy. Write down three kinds of rules: auto-file small, routine items in a clear category, such as a monthly software subscription; flag for review anything over a threshold you set, anything in Misc, and any receipt read with low confidence; and never approve reimbursements, edit past months, or send reports to your accountant without you saying so. Put these limits in the SKILL.md file itself, in plain language, so the agent follows them every time.
Step 5: Build the monthly report template
Give the skill one report template and let it fill the same shape every month: a one-line summary with the month’s total, a table of spending by category, the five largest expenses, flagged items waiting for your decision, and a short note on anything unusual, such as a category that doubled since last month. Keep the receipt photos filed with the report, organised by month, so any line traces back to its source.
Step 6: Test on fake receipts, then go live
Before the skill touches real expenses, test it with your test set. Ask it to process five receipts and produce a report, then check every line — vendor, date, total, category — and its flagging behaviour on one deliberately blurry photo. Fix the instructions where it guessed, or picked the wrong category.
Then run it for one real week with you reviewing every line. If the week is clean, move to a monthly review. If the same mistake appears twice, fix the rule in SKILL.md rather than fixing the output each time.
Once the skill works for one person, add it to your small business skill library so the whole team uses the same categories and report shape. Read our guide on how to audit an agent skill first — a skill reading financial documents deserves the same safety check as any tool touching your money.
Tips for small teams
- Photograph receipts the same day: A receipt photographed today is legible. One found in a jacket pocket next month often is not.
- Keep categories boring: If two categories overlap, merge them. Ten honest categories beat twenty clever ones.
- Review monthly, not yearly: A monthly review takes twenty minutes and catches drift early.
Frequently asked questions
Can the skill post expenses straight to my accounting software?
Only if you build that connection and give it permission. For most small teams that is not the right first step: start with the skill producing a report you review, then enter the approved lines yourself. Add a direct connection only after a month of clean reports, with a human approval step before anything is posted.
What happens when a receipt photo is unreadable?
A well-written skill flags it and asks you to re-photograph or type the details in. Never let a skill guess a total from a blurry photo, because a guessed number looks exactly like a real one in a report.
How long does a first expense skill take to build?
One focused afternoon covers the categories, the SKILL.md file, the report template, and a test run on five receipts. Allow an extra week of daily use with review before you trust it on a full month.
Sources
- Anthropic, Agent Skills overview: https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview
- Anthropic, Agent Skills open standard: https://agentskills.io



