Individual skill
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.
finance/month-end-close/skills/month-end-close/SKILL.md
Source commit 9ef0c3c213932e645cc5cbeeb3c35c3a762a2437
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 29,448
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- anthropic-claude Repository topic
- claude-ai Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- claude-code-skills Repository topic
- ai-coding-agent Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- openai-codex Repository topic
- writing Derived category
- productivity Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,649 bytesSKILL.mdcore · 5,649 bytesSKILL.mdcore · 5,649 bytesSKILL.mdcore · 5,649 bytesassets/bank_statement.example.csvasset · 213 bytesassets/close_plan.example.jsonasset · 2,070 bytesassets/flux_input.example.csvasset · 654 bytesassets/gl_cash.example.csvasset · 308 bytesassets/reconciliation_signoff.mddoc · 1,267 bytesreferences/close_calendar_and_benchmarks.mddoc · 4,454 bytesreferences/flux_analysis_and_materiality.mddoc · 4,106 bytesreferences/reconciliation_standards.mddoc · 4,304 bytesscripts/close_calendar_planner.pyruns · 11,226 bytesscripts/flux_analyzer.pyruns · 9,167 bytesscripts/reconciliation_matcher.pyruns · 16,973 bytes
Read excerpt
# 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
```bash
# 1 - Calendar: dependency order, critical path, owners, reviewers, load.
python scripts/close_calendar_planner.py --plan close_plan.json