From month-end-closer
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/month-end-closer:variance-commentaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Given current-period actuals, prior-period actuals, and budget for the same scope, produce a commentary table.
Given current-period actuals, prior-period actuals, and budget for the same scope, produce a commentary table.
Flag a line for commentary if either is true:
| 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%)."
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.
The commentary table plus a short narrative (3–5 sentences) summarizing the period's biggest movers.
npx claudepluginhub pa4uslf/financial-services-codex --plugin month-end-closerGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
31plugins reuse this skill
First indexed Jun 3, 2026
Showing the 6 earliest of 31 plugins