variance-commentary
Write flux commentary for every P&L and balance-sheet line over threshold — current vs prior period and vs budget, with the driver explained from underlying activity. Use for the month-end close package and management reporting.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Variance commentary
Given current-period actuals, prior-period actuals, and budget for the same scope, produce a commentary table.
Threshold
Flag a line for commentary if either is true:
- Absolute variance ≥ the firm's materiality threshold (use the provided value; default 5% of the line or a fixed floor, whichever is greater)
- The line is on the "always comment" list (revenue, headcount cost, cash)
For each flagged line
| Column | Content |
|---|---|
| Line | Account or caption |
| Current / Prior / Budget | The three values |
| Δ vs prior and Δ vs budget | Amount and % |
| Driver | One sentence explaining the movement from underlying activity — not a restatement of the number |
A driver explains why, not what: "Cloud spend up $1.2M on incremental GPU reservations for the May launch" — not "Cloud spend increased $1.2M (18%)."
Sourcing the driver
Look at the activity behind the line (journal-source breakdown, vendor mix, headcount delta, volume × rate) via the internal-gl MCP. If the driver isn't clear from the data, write "driver unclear — flag for controller" rather than inventing one.
Output
The commentary table plus a short narrative (3–5 sentences) summarizing the period's biggest movers.
- Repository
- anthropics/financial-services
- Commit
eb0c1ea
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.