Keep customers from churning — before they decide to leave
Catch at-risk customers early and keep them — with five chained retention skills.
A clean month-end close is only half the job — the other half is explaining what the numbers mean. Five free Agent Skills orchestrate the close, explain variances, write the narrative, prep for audit, and adjudicate expenses. Learn the frameworks and run them in Claude.
Free to try. One click loads the skill into Claude or ChatGPT, with no account and no setup.
Closing the books means reconciling every account and producing accurate financial statements for the period. That’s necessary — but on its own it’s just numbers. The half that actually drives decisions is the explanation: why did we beat or miss plan, what does it mean, and what should leadership do about it? A perfect close that nobody understands changes nothing.
That’s why the strongest finance teams treat the close and the story as one job. Get the close right and fast (so there’s time to think), then translate the results into a narrative executives can act on. These skills encode both — the mechanics of a controlled close and the frameworks for turning its output into insight — so finance moves from scorekeeper to advisor.
The skill isn’t magic. It encodes proven frameworks anyone can learn. Here’s the method itself, so you understand what it’s doing for you.
The month-end close is a recurring, time-sensitive process across many people and systems — and in most companies it lives in someone’s head or scattered spreadsheets. A structured close runs in four phases: Pre-Close (Day −2 to 0 — cutoffs, accruals, reminders), Transaction Close (Day 1–3 — post entries, close sub-ledgers, AR/AP, inventory), Reconciliation & Review (Day 3–5 — reconcile, analyze, investigate, approve), and Reporting & Sign-off (Day 5–7 — financial statements, management review).
Modeling the close this way — with explicit dependencies, timing, and sign-offs — is what turns it from a stressful monthly scramble into a consistent, controlled process. It also makes the close auditable: a documented process with sign-offs is exactly what auditors want to see.
Every finance team spends hours answering “why are we off budget?” The hard part isn’t calculating the variance — it’s deciding what’s material, investigating the root cause, and translating it into business language. The difference is everything:
Finance often delivers “Revenue was $50K under budget.” What a stakeholder actually needs is “We missed revenue because the Smith deal slipped to next month; pipeline remains strong.” Or: not “Marketing overspent 15%” but “Marketing pulled Q3 spend forward for the launch, which drove the revenue beat — net positive.” The framework moves you from numbers to narrative — materiality first, then root cause, then a business-terms explanation an executive can act on.
Use any one on its own, or chain them. Each hands its output to the next. Every one is free in the public library.
Runs the close as a structured process — phases, dependencies, timing, and sign-offs — instead of scattered spreadsheets and tribal knowledge.
Explains why you’re off budget in business terms — materiality assessment, root-cause investigation, and executive-ready language.
Turns the numbers into the story — board decks, investor letters, management reporting for non-financial stakeholders.
Gets you ready for external audit — organized documentation, anticipated questions, SOX and PBC readiness — before fieldwork starts.
Applies expense policy to the gray-area cases consistently, so approvals don’t depend on who’s reviewing.
Every month, for starters — but especially when the close is a scramble, when “why are we off budget?” eats your week, or when board and investor reporting is a fire drill each quarter.
They cover the whole month-end job — both halves of it. The orchestrator runs the close itself as a controlled, phased process. Then the reporting layer does the part finance is actually judged on: the variance narrator explains why you’re off plan, and the narrative generator turns the numbers into a story for the board and investors.
Around that, audit-readiness-preparer keeps you ready for external audit year-round, and expense-policy-adjudicator makes day-to-day expense approvals consistent. Together they take you from raw ledgers to a signed-off, well-explained, audit-ready close.

Real prompts, and what the skill hands back.
“Revenue came in $80K under plan and marketing was 12% over. Assess materiality and draft the variance explanation for the board.”
A materiality assessment, a root-cause investigation, and a business-terms narrative connecting the marketing over-spend to the revenue picture — board-ready.
“Build me a month-end close checklist for a SaaS company with a 5-day close — phases, owners, and sign-offs.”
A four-phase close calendar (pre-close → transaction → reconciliation → reporting) with activities, dependencies, and sign-off gates mapped to a 5-day timeline.
Pre-close → transaction → reconciliation → reporting, with dependencies and sign-offs — controlled, not chaotic.
Variance work starts by deciding what actually matters, so you explain the signal, not the noise.
The story translates results into business terms an executive can act on.
A documented, signed-off process is exactly what auditors want — readiness is a by-product.
Expense adjudication and close sign-offs remove “depends who’s reviewing” inconsistency.
The flow is close → explain → narrate, with audit-readiness and expense adjudication as the controls around it: month-end-close-orchestrator produces clean numbers → financial-variance-narrator explains them → financial-narrative-generator tells the story → audit-readiness-preparer keeps it defensible → expense-policy-adjudicator keeps inputs consistent. Run the whole cycle, or just the reporting layer if your close is already solid.
Run the skills in Claude and customize each with your accounts, deadlines, and policies:
Already connected your library to Claude? Tell it: “Use the month-end-close-orchestrator skill (and the others above) from the agentman_skills MCP server.”
Not connected yet? The Try in Claude / ChatGPT button loads the first one from the public library, with no setup. Or connect your library.
Click “Try in Claude / ChatGPT” above, or — if you’ve connected your library — tell Claude: “Use the month-end-close-orchestrator skill from the agentman_skills MCP server.” Add the others by slug as you go.
Run month-end-close-orchestrator and customize the four-phase checklist with your accounts, deadlines, and sign-offs — turning the close into a repeatable, controlled process.
Feed budget-vs-actuals to financial-variance-narrator — it assesses materiality, investigates root cause, and drafts the business-terms explanation.
Run financial-narrative-generator to turn the results into a board deck, investor letter, or management report for non-financial readers.
Use audit-readiness-preparer to keep documentation, PBC lists, and SOX evidence organized — so audit fieldwork is smooth, not a scramble.
Run expense-policy-adjudicator on the gray-area reimbursements so approvals are consistent regardless of who reviews them.
That’s the work of a controller plus an FP&A analyst — assembled from five free skills you customize to your books.
One click loads the skill into Claude or ChatGPT. No account, no setup.
No. Run the orchestrator alone to structure your close, or the variance narrator + narrative generator to sharpen reporting. Chained, they cover close-to-narrative end to end, but each stands alone.
The variance narrator applies a framework: assess materiality (what actually matters), investigate root cause, then translate into business language. It moves you from “revenue was $50K under budget” to “the Smith deal slipped to next month; pipeline is strong.”
Yes. The audit-readiness-preparer organizes documentation, anticipates auditor questions, and covers SOX and PBC readiness before fieldwork — and a documented, signed-off close process is itself what auditors want to see.
No. Click “Try in Claude / ChatGPT” above and the first skill loads from our public library — no setup. Clone the skills to customize them to your accounts and policies and share them.