An agent skill for monthly bookkeeping close is a reusable set of instructions that tells Claude how to gather a month of receipts, match them against your bank and card statements, and build a reconciliation report you review before anything is filed. Build it once, and your team runs the same routine every month. Here is how, in two hours.
What the skill does (and what it does not)
Every small business closes the month the same way: collect receipts, check statements, chase the missing ones, and summarise what came in and went out. The mistakes come from the same places too — a receipt nobody filed, a subscription charged twice, a transfer counted as income.
An agent skill captures that routine in one folder. Anthropic describes Agent Skills as reusable, filesystem-based resources that give Claude domain-specific expertise, each starting with a SKILL.md file. The agent first sees only the short name and description (roughly 100 tokens per skill), then loads the full instructions when a task matches, a pattern called progressive disclosure.
Your close skill does four things: gather the month’s receipts, match each one to a statement line, flag anything unmatched, and build a report. It prepares the close; it never files, posts, or moves money.
Before you start
Gather five things: your category list (the 8 to 12 you actually use); one receipts inbox, a single shared folder where every receipt lands; your bank and card statements as exports, not screenshots; one owner, who reviews the report and decides on flagged items; and last month’s statements and receipts as a test set.
If your data is messy, fix the export first: a skill built on bad data writes confident reports with wrong numbers. Check that every receipt file name carries a date and statements cover the whole month. Most close mistakes trace back to a statement that ended on the 29th.
Step 1: Define what “closed” means
Write it down first: a close is finished when every statement line has a matching receipt or explanation, every receipt has a category, and the report shows one total per category plus open items. Put that definition in the SKILL.md file itself.
| Check | Pass rule |
|---|---|
| Every statement line matched | Receipt found, or flagged with a reason |
| Every receipt categorised | From your list, never invented |
| Unmatched items listed | Each one named with amount and date |
| Report totals add up | Category totals equal the statement totals |
Add one catch-all rule: if the skill cannot read a receipt clearly or match a statement line with confidence, it must flag the item instead of guessing. A flagged line takes a minute to fix, while a silently wrong total can sit in your books until tax time.
Step 2: Create the skill folder and SKILL.md file
A skill is a folder containing a SKILL.md file. Create a folder named monthly-bookkeeping-close for it. Where you save it decides who uses it: ~/.claude/skills/ makes it available in all your own Claude Code projects, while .claude/skills/ inside a shared repository gives it to your whole team. On claude.ai, upload custom skills as zip files on a Pro, Max, Ultra, Team, or Enterprise plan with code execution on. Skills do not sync across surfaces, so install it where your team works.
Step 3: Write the frontmatter
Every SKILL.md starts with a short YAML frontmatter block between two lines of three dashes, holding the skill’s name and a description. The name is at most 64 characters, lowercase letters, numbers, and hyphens only, and it cannot contain the words “anthropic” or “claude”. The description is at most 1,024 characters and must say both what the skill does and when to use it. That is what the agent reads to decide whether to load it.
For example: “Reconciles a small business month-end close: matches receipts to statements and builds a report for review. Use when the user asks to close the month.” Keep the name short and lowercase with hyphens, such as monthly-bookkeeping-close.
Step 4: Write the close workflow
Below the frontmatter, write the procedure as numbered steps: gather every receipt and statement line for the month; match receipts to statement lines by amount and date, allowing a small window for late card charges; categorise each matched item; then list every unmatched line and uncategorised receipt as open items with amount and date.
Add three rules that keep the skill safe:
- Draft only, never post. A human approves the report before anything enters your books.
- Flag, do not guess. A missing receipt or mismatched amount stops the line; the skill never invents a category or a total.
- Cite the source. Every report line names its receipt file or statement line, so a reviewer can check it in seconds.
Step 5: Add a reconciliation template
Give the skill one report template to fill the same way every month: a summary, a table of spending by category, the five largest expenses, the open items waiting for your decision, and a short note on anything unusual. File receipts with the report, organised by month, so any line traces back to its source.
If you already use an expense-tracking skill, reuse its category list and receipt inbox so the two skills agree. Pair it with our invoice-chasing skill to close the loop on late payments before the month ends.
Step 6: Test on last month, then go live
Before the skill touches a live close, run it on last month’s receipts and statements and compare every line with the close your team did. A skill that passes on real data is ready.
Also run a safety check: use skills only from trusted sources, because a skill can run code and read files. Confirm yours contains no secrets, no network calls, and no permission it does not need.
Then run it for one real month, reviewing every line. If the month is clean, move to monthly spot checks. If the same mistake appears twice, fix the rule in SKILL.md. A skill that drifts from the real process is worse than no skill, because the team trusts it.
Tips for small teams
- Close on a fixed day: Pick the 5th of the month and stick to it, while the month is still fresh.
- File receipts the same day: One 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.
Frequently asked questions
Can the skill post entries straight to my accounting software?
Only if you build that connection. For most small teams that is not the right first step: start with a report you review, then enter the approved lines by hand. Add a direct connection only after a month of clean reports.
What happens when a receipt is missing?
A well-written skill lists the statement line as an open item and asks you to find the receipt or write a one-line explanation. Never let a skill invent a receipt to make the totals match.
Sources
- Anthropic, Agent Skills overview — https://docs.claude.com/en/docs/agents-and-tools/agent-skills/overview
- Anthropic, “Equipping agents for the real world with Agent Skills” — https://www.anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills
- Agent Skills open standard — https://agentskills.io



