budget-review
Skill1 starsChanged 2 months agoMITView on GitHub
Review, fill in, and balance a monthly budget kept in Apple Numbers using the Digits MCP tools. Use when the user says "review my budget", "update my budget", "fill in my budget", "balance my budget", "how am I doing this month", or asks to add expenses, income, or totals to a Numbers budget spreadsheet.
In this repository2 other files it gives its agents.
- data-cleanupSkill
- monthly-reportSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Locate the budget: Call numbers_list_documents.
- Very specific: line 18
Orient: Call numbers_list_sheets (budgets are often one sheet per month — pick the current month unless told otherwise) and …
- Very specific: line 22
Read the current state: Call numbers_read_table with include_formulas: true.
- Distinctive: line 33
Collect amounts conversationally: Ask for missing numbers in one batch, not one question at a time.
- Very specific: line 36
Write in one batch: Use a single numbers_set_cells call with all updates.
- Distinctive: line 49
Read before every write session.
- Distinctive: line 50
Never overwrite a non-empty cell without telling the user first.
- Very specific: line 51
Prefer one large numbers_set_cells batch over many small ones.
- Distinctive: line 54
If a target sheet for the current month doesn't exist, offer to build it by copying the structure of the most recent month's sheet.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Budget Review (Apple Numbers)
Drive a monthly-budget workflow against a live Numbers spreadsheet using the
Digits MCP tools (numbers_*). Never guess at the spreadsheet's contents —
always read before writing.
Workflow
- Locate the budget. Call
numbers_list_documents. If empty, ask the user for the file path and callnumbers_open_document. If multiple documents are open, ask which one is the budget. - Orient. Call
numbers_list_sheets(budgets are often one sheet per month — pick the current month unless told otherwise) andnumbers_list_tablesto get table names and dimensions. - Read the current state. Call
numbers_read_tablewithinclude_formulas: true. Build a mental model: where income lines are, where expense lines are, which cells hold amounts, which hold totals. - Gap analysis. Report to the user, leading with what's already in good
shape, then:
- expense/income lines with no amount filled in
- totals that are typed constants instead of formulas
- missing common categories (savings, debt payments, emergency fund)
- arithmetic that doesn't add up
- Collect amounts conversationally. Ask for missing numbers in one batch, not one question at a time. Accept approximations.
- Write in one batch. Use a single
numbers_set_cellscall with all updates. Use formulas, not computed constants, for derived cells — e.g.=SUM(F4:F14)for a total — so the sheet stays live when the user edits it by hand later. - Verify. Re-read the table and confirm the totals computed correctly. Show the user income − expenses = surplus/deficit.
- Save only with permission.
numbers_set_cellsedits are in-memory and undoable. Ask before callingnumbers_save_document.
Rules
- Read before every write session; the user may have edited the sheet.
- Never overwrite a non-empty cell without telling the user first.
- Prefer one large
numbers_set_cellsbatch over many small ones. - Money amounts: write plain numbers (2515.50), never formatted strings ("$2,515.50") — formatting belongs to the cell, not the value.
- If a target sheet for the current month doesn't exist, offer to build it by copying the structure of the most recent month's sheet.
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.

