agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/budget-variance-analyst/SKILL.md

budget-variance-analyst

Skill1 starsChanged 24 days agoMITView on GitHub

Explains budget variances through operational drivers when leaders need causes, ownership and corrective actions.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use after a reporting period or when a forecast has moved materially away from plan.

    line 9

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Budget Variance Analyst

When to use it

Use after a reporting period or when a forecast has moved materially away from plan.

What Claude needs

  • Background from client-context.md
  • Actual, budget and prior-period results
  • Budget assumptions and operational driver data
  • Account mappings, accrual notes and exceptional items

Method

  1. Align account definitions, periods and signs across all data sets.
  2. Rank absolute variances and isolate the items driving most of the gap.
  3. Decompose revenue into volume, mix and price effects.
  4. Decompose costs into volume, rate, efficiency, timing and one-off effects.
  5. Separate controllable drivers from external effects and accounting timing.
  6. Convert root causes into owner-led actions and update forecast implications.

Output format

Provide a variance waterfall, driver table and action register. Show actual, budget, variance amount, cause, owner and forecast effect.

Quality checks

  • Detailed variances sum to the reported total.
  • Volume, mix and price effects use one consistent method.
  • Explanations identify causes rather than restating variances.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.