Agent skill · Design & Presentation

budget-tracker-design

Design a budget-vs-actuals tracker that stays alive past February — the category grain that matches real statements, the variance view that answers 'are we okay', the update ritual small enough to survive, and the honest handling of irregular expenses. Use when asked build me a budget spreadsheet, track team spend against budget, why do we always blow the budget invisibly, or design a household/project budget tracker. Produces the tracker structure, the variance logic, the irregulars ledger, and the monthly fifteen-minute ritual.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill budget-tracker-design --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/budget-tracker-design/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Budget Tracker Design Skill Budget trackers die two deaths: too granular (forty categories nobody can code a coffee receipt into — abandoned by February) or too vague (three buckets that hide every overrun until it's structural). The living tracker matches its grain to *how spending actually arrives* (statement lines, invoices), answers one question at a glance — "are we okay, and where not?" — handles irregular expenses honestly (the annual insurance bill is not a "shock"), and costs fifteen minutes a month, because the ritual's survivability is the design's real constraint. ## What This Skill Produces - **The structure** — categories at statement-grain (8–15, not 40), the month × category grid, budget column with its source - **The variance view** — actual vs. budget with the month-and-YTD dual read, conditional signals at honest thresholds - **The irregulars ledger** — annual/lumpy expenses spread as monthly accruals so they stop being surprises - **The ritual** — the fifteen-minute monthly update, sourced from statements, calendared ## Required Inputs Ask for these if not provided: - **The scope** — household, team, or project budget; and the currency of pain ("we get surpris

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: The Design Rules
  4. Output Format
  5. Structure
  6. Variance View
  7. Irregulars Ledger
  8. The Ritual (15 min, calendared)
  9. Quality Checks
  10. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the budget-tracker-design skill do?

Design a budget-vs-actuals tracker that stays alive past February — the category grain that matches real statements, the variance view that answers 'are we okay', the update ritual small enough to survive, and the honest handling of irregular expenses. Use when asked build me a budget spreadsheet, track team spend against budget, why do we always blow the budget invisibly, or design a household/project budget tracker. Produces the tracker structure, the variance logic, the irregulars ledger, and the monthly fifteen-minute ritual.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill budget-tracker-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.

Keep going