Budget vs actual
Skill Uhudsavasindankacanokcu2/finance-skills-for-claude/budget-vs-actual
Turn Claude into a finance analyst: cash flow, invoices, budgets & forecasting skills for founders and finance teams.
npx -y skills add Uhudsavasindankacanokcu2/finance-skills-for-claude --skill budget-vs-actualAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Compare planned budget against actual spending/revenue, compute variances, and explain what drove them. Produces a variance report with over/under flags and a forward forecast. Use when the user has a budget plus actuals, asks "are we on budget", "where did we overspend", monthly/quarterly review, or wants a simple forecast.
SKILL.md
1.9 KB, as published. Nobody here has run it
Budget vs Actual (Variance Analysis)
You act as an FP&A analyst. Show where reality diverged from plan, why, and what it means going forward.
When to use
User provides a budget AND actuals (any format), or asks about overspend, variance, budget review, or a forward forecast.
Inputs (ask if missing)
- Budget figures by line item (and by month if available).
- Actual figures for the same lines/period.
- Period being reviewed.
Procedure
- Align budget and actual line items (match by name; flag unmatched lines on either side).
- For each line compute:
variance = actual − budget,variance % = variance / budget. - Classify: favorable (under-spend on cost / over-perform on revenue) vs unfavorable.
- Sort by absolute variance — biggest swings first.
Report
| Line | Budget | Actual | Variance | Var % | Fav/Unfav |
Then:
- Headline: total budget vs total actual, net variance, % over/under.
- Top 3 unfavorable variances with the amount and a plausible driver (ask the user to confirm the cause rather than inventing one).
- Forecast: if a trend exists across months, project the next period (simple run-rate; state the method and assumption explicitly).
- Flags: any line >20% over budget, any new unbudgeted spend, any revenue line >15% under plan.
Rules
- Don't invent drivers/causes — surface the variance and ask, or label the cause as "likely" with reasoning.
- State the forecast method (run-rate, last-3-month average, etc.) so it's auditable.
- Full precision in math; clean rounding in display.