From personal-finance
This skill should be used when the user asks to "create a budget", "analyze spending", "categorize transactions", "track expenses", "manage cash flow", "pay off debt", "compare debt payoff methods", or mentions budgeting frameworks like zero-based budgeting, 50/30/20, or envelope budgeting. Provides budgeting methodology, transaction categorization guidance, and spending analysis tools.
How this skill is triggered — by the user, by Claude, or both
Slash command
/personal-finance:budgetingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Provide structured budgeting guidance using established frameworks. Categorize transactions from bank/credit card CSV exports, analyze spending patterns, and build actionable budgets. All advice is educational — recommend a certified financial planner for personalized financial guidance.
Provide structured budgeting guidance using established frameworks. Categorize transactions from bank/credit card CSV exports, analyze spending patterns, and build actionable budgets. All advice is educational — recommend a certified financial planner for personalized financial guidance.
Every dollar of income is assigned a purpose. Income minus all allocations equals zero. When overspending occurs in one category, pull from another — "roll with the punches." Best for people who want full control and visibility.
Split after-tax income into needs (50%), wants (30%), and savings/debt (20%). "Needs" means obligations that don't go away if income drops: housing, utilities, groceries, insurance, minimum debt payments. Everything else is a want. In high-cost-of-living areas, the needs portion often exceeds 50% — adjust ratios rather than mislabeling wants as needs.
Assign spending caps to categories. When the envelope is empty, stop spending in that category until next period. Digital equivalent: category tracking with hard limits. Pairs well with ZBB for implementation.
See references/budget-frameworks.md for detailed methodology breakdowns.
Follow this sequence when processing bank/credit card CSV exports:
references/csv-formats.md for known formats and column-detection heuristics.references/merchant-categories.md for patterns.scripts/spending_summary.py or produce equivalent output: totals by category, percentage of spending, percentage of income, transaction counts, averages.Primary categories with common subcategories:
Irregular or annual expenses divided into monthly allocations. Prevent "surprise" large expenses from blowing the budget.
Examples: car registration, annual insurance premiums, holiday gifts, vacation, home maintenance reserve, annual subscriptions (domains, software).
Calculate monthly amount: annual cost / 12. Start accumulating immediately even if the expense is months away.
Pay attention to when income arrives versus when bills are due. Biweekly pay creates two "extra" paychecks per year. Aligning bill due dates with pay dates prevents overdrafts. Two-paycheck months handle regular expenses; three-paycheck months accelerate goals.
Two primary strategies:
Use scripts/debt_payoff.py to calculate and compare both approaches side-by-side.
scripts/spending_summary.py — Analyze categorized transactions: totals, percentages, monthly comparisons, threshold alertsscripts/debt_payoff.py — Compare avalanche vs snowball payoff schedules with total interest and timelinereferences/merchant-categories.md — Merchant-to-category lookup table with regex patternsreferences/budget-frameworks.md — Detailed methodology for each budgeting frameworkreferences/csv-formats.md — Bank/credit card CSV format documentation and detection heuristicsnpx claudepluginhub bloknayrb/claudestuff --plugin personal-financeGenerates avalanche (highest interest first) or snowball (smallest balance first) debt payoff plans with month-by-month payment schedules from transaction data.
Creates or overhauls a personal/household budget using zero-based and 50/30/20 methods. Guides users through income calculation, expense tracking, and savings prioritization.
Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.