expense-sheet-design
Design an expense-tracking sheet that survives real receipts — the capture-at-spend habit, the category set that matches reimbursement or tax rules, the receipt-link discipline, and the month-end close that takes minutes because the work happened at spend-time. Use when asked track my business expenses, build an expense sheet for the team, get ready for reimbursement/tax season, or my shoebox of receipts needs a system. Produces the sheet structure, the capture ritual, the category mapping to the real downstream rules, and the month-end close.
npx skills add mohitagw15856/pm-claude-skills --skill expense-sheet-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Expense Sheet Design Skill Expense tracking has one law: it happens at spend-time or it happens badly. The March reconstruction — a shoebox of receipts, a statement, and archaeology — produces worse data at fifty times the cost of a fifteen-second capture habit. The sheet's design serves that habit: columns light enough to fill from a phone, categories that map to the *downstream consumer's* rules (the reimbursement policy, the tax return's lines — not aesthetic taxonomy), receipts linked not shoeboxed, and a month-end close that's minutes because every entry already exists. ## What This Skill Produces - **The sheet structure** — the capture-light column set (date, amount, merchant, category, receipt-link, notes-if-odd), one row per expense - **The category set** — mapped to the actual downstream: the employer's reimbursement categories, or the tax return's deduction lines (jurisdiction-flagged), never invented ontology - **The capture ritual** — the fifteen-second at-spend habit: photograph receipt → one row → done - **The month-end close** — reconcile against the statement, chase the gaps, subtotal by category, file the export ## Required Inputs Ask for these if not provided: -
- What This Skill Produces
- Required Inputs
- Framework: The Design Rules
- Output Format
- The Structure
- Category Mapping
- The Capture Ritual
- Month-End Close (15 min)
- Quality Checks
- Anti-Patterns
What does the expense-sheet-design skill do?
Design an expense-tracking sheet that survives real receipts — the capture-at-spend habit, the category set that matches reimbursement or tax rules, the receipt-link discipline, and the month-end close that takes minutes because the work happened at spend-time. Use when asked track my business expenses, build an expense sheet for the team, get ready for reimbursement/tax season, or my shoebox of receipts needs a system. Produces the sheet structure, the capture ritual, the category mapping to the real downstream rules, and the month-end close.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill expense-sheet-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.