Explain financial variance through supported business drivers.
Trace budget, forecast, or period differences to reconciled evidence while keeping assumptions and professional sign-off visible.
What this playbook provides
This skill structures finance analysis around the question a reviewer actually needs answered: what changed, which driver supports the explanation, and what remains uncertain. It prevents a fluent narrative from replacing reconciliation and requires qualified review before the output is relied upon.
- A reconciled variance table
- Supported driver commentary
- Explicit caveats and open questions
Example compositions using this skill
Where useful, a skill adds reusable method to a composition built primarily from connectors, agent instructions, a deliverable, and an approval boundary.
Month-end close review
Reconcile payout activity against the approved close records, explain mismatches, and prepare a review packet for qualified sign-off.
See the workflow
Receivables review
Find overdue invoices, assemble recent account and correspondence context, and prepare a prioritized follow-up list without sending messages.
See the workflow
Spend anomaly watch
Read daily payment and refund activity, compare each category against its recent baseline, and flag only the movements that are large enough to need an explanation.
See the workflowForecast variance brief
Compare actual results against the approved forecast at month-end, attribute each material variance to a cause, and prepare a brief with the assumptions that need revisiting.
See the workflowApply the variance analysis playbook to recurring work.
Each one arrives with a persona, standing instructions, a wake-up schedule, and its connectors chosen. Nothing runs until you add it.