Agent skill · alirezarezvani
month-end-close
Use when running, planning or speeding up a month-end (or quarter-end) close — building or reviewing the close checklist and calendar, reconciling a bank statement or sub-ledger to the general ledger, writing or reviewing flux (variance) explanations, or finding why the close takes too many days. Orders close tasks by dependency and finds the critical path, proves each reconciliation and ages what is left, and refuses to sign off material fluctuations explained with boilerplate.
What it needs
About 3k tokens when loaded.
What this skill does
Month-End Close Portability: 3 stdlib scripts, no network, no ERP connection. Export CSV or JSON; the scripts plan, prove and gate. Not accounting or audit advice. Thresholds and aging limits are your policy; the scripts make you state them. A slow close is rarely slow everywhere. One chain of dependent tasks sets the close date, reconciliations "agree" without a proof, and flux review accepts "timing" as a reason. Each script attacks one of those. Workflow Step 1 schedules each task as soon as its predecessors finish, then checks the plan against people: one person booked for 1.5 days on WD1 is a plan that will slip. Speed up the critical path, nothing else. Step 2 matches by reference, then by amount within a date window, then pairs digit transpositions (7,980 vs 7,890) into one correcting entry. What is left is a reconciling item: in the GL only (timing) or in the source only (book a journal entry). Opening-balance rows are balances, not transactions: when the two sides open at different amounts, that difference came from last month and blocks sign-off until it is traced there; it is never booked this period. The proof must close to zero. Step 3 marks an account material when it passes your threshold rule, flips sign, or appears or disappears. Its explanation fails if it is missing, stock ("timing", "in line with expectations"), or has no number in it. The gates block on (exit 4) 1. A task with no owner, or a key control with no reviewer or reviewed by its preparer. 2. A plan whose critical path ends after the target workday. 3. A reconciliation that does not prove, or an item older than the stale limit (default 90 days, policy). 4. Preparer and reviewer being the same person, or a flux reviewer who owns the line. 5. A material fluctuation with a missing, boilerplate or unquantified explanation. Hard rules A sign-off is not evidence of review. Record what was checked and where the support is. Never plug a reconciliation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/month-end-close--0ff1fa