close-management
Skill1 starsChanged 7 months agoMITView on GitHub
Manage the month-end close process with task sequencing, dependencies, and status tracking. Use when planning the close calendar, tracking close progress, identifying blockers, or sequencing close activities by day. Trigger with "close checklist", "close status", "what's blocking close", "close timeline", or "day X close tasks".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- insight68/Skillstheir own version, first seen Nov 8, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- alebgl77/claude-inctheir own version, first seen Jul 28, 2026
- GAJETOso/financeskillstheir own version, first seen May 2, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- anthropics/knowledge-work-plugins★ 36ksame name
- GAJETOso/financeskills★ 47same name
- alebgl77/claude-inc★ 21same name
- insight68/Skills★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
Hard deadline: When must the close be finalized (e.g., WD+5 for SEC filers).
- Distinctive: line 46
Run preliminary trial balance
- Distinctive: line 79
All subledger close MUST complete before trial balance is final.
- Distinctive: line 80
All JEs MUST be posted before financial statement generation.
- Distinctive: line 146
Always sequence tasks by dependency, not just by day.
- Very specific: line 151
When reporting status, use RED/YELLOW/GREEN at the task level so leadership can scan quickly.
- Distinctive: line 152
Keep the close checklist as a living document.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Month-End Close Management
Manage the full month-end close process: build the close calendar, sequence tasks with dependencies, track status, surface blockers, and report progress to stakeholders.
Workflow
Step 1: Determine Close Parameters
Gather the close context:
- Period: Which month is closing (default: most recent completed month).
- Business days: How many business days is the close window (typical: 5-7).
- Hard deadline: When must the close be finalized (e.g., WD+5 for SEC filers).
- Team structure: Who owns which close tasks (controller, staff accountants, FP&A, tax).
Step 2: Build or Load the Close Checklist
Organize tasks into a standard close sequence by business day:
Day 1 (WD+1): Preliminary
- Cut off AP/AR subledgers
- Run preliminary trial balance
- Post recurring journal entries (depreciation, amortization, prepaids)
- Complete bank reconciliations
Day 2 (WD+2): Accruals & Adjustments
- Post accrual journal entries (payroll, utilities, professional fees)
- Complete intercompany reconciliations and eliminations
- Post FX revaluation entries
- Reconcile payroll clearing accounts
Day 3 (WD+3): Review & Reconciliation
- Complete all balance sheet reconciliations
- Perform flux analysis on P&L accounts
- Review and approve all manual journal entries
- Reconcile revenue to billing system
Day 4 (WD+4): Financial Statements
- Generate draft financial statements (P&L, BS, CF)
- Prepare variance analysis vs. budget and prior period
- Review consolidation entries
- Tax provision estimate
Day 5 (WD+5): Finalize
- Management review of financial statements
- Record any final adjusting entries
- Lock the period in the ERP
- Distribute close package to stakeholders
Step 3: Track Dependencies
Map task dependencies to identify the critical path:
- Bank reconciliation MUST complete before cash flux analysis.
- All subledger close MUST complete before trial balance is final.
- All JEs MUST be posted before financial statement generation.
- Intercompany MUST reconcile before consolidation.
Flag tasks where a dependency is incomplete and the dependent task is due.
Step 4: Identify and Escalate Blockers
For each incomplete task past its target day:
- Owner: Who is responsible.
- Blocker reason: Missing data, system issue, dependency, or capacity.
- Impact: What downstream tasks are affected.
- Resolution path: Specific next action to unblock.
- Escalation: Whether controller or CFO attention is needed.
Step 5: Generate Status Report
Produce a close status summary for the current state.
Output Format
## Month-End Close Status: [YYYY-MM]
**Close window**: WD+1 through WD+[N] | **Current day**: WD+[X]
**Overall status**: ON TRACK / AT RISK / DELAYED
### Progress Summary
| Day | Total Tasks | Complete | In Progress | Blocked | Not Started |
|-------|-------------|----------|-------------|---------|-------------|
| WD+1 | 8 | 8 | 0 | 0 | 0 |
| WD+2 | 6 | 4 | 1 | 1 | 0 |
| WD+3 | 5 | 0 | 2 | 0 | 3 |
### Blockers
| # | Task | Owner | Blocker | Impact | ETA |
|---|--------------------------|-------------|-----------------|---------------------|--------|
| 1 | IC reconciliation | J. Smith | Waiting on sub | Delays consolidation| WD+3 PM|
### Completed Today
- [x] Bank reconciliation (all accounts) - J. Doe
- [x] Depreciation JE posted - M. Lee
### Due Next
- [ ] Payroll accrual JE - K. Park (WD+2)
- [ ] Revenue rec review - S. Chen (WD+2)
### Key Metrics
- **Journal entries posted**: 24 / 32
- **Reconciliations complete**: 18 / 25
- **Open review items**: 3Examples
User: "Build a close checklist for March 2026 with a 5-day window" Action: Generate the full sequenced checklist with all tasks organized by business day, dependencies noted, and owner placeholders.
User: "What's blocking the close?" Action: Review all in-progress and blocked tasks, identify root causes, map downstream impacts, and recommend resolution actions.
User: "Close status for WD+3" Action: Produce the status report showing progress through day 3, highlighting anything behind schedule.
Best Practices
- Always sequence tasks by dependency, not just by day. A task with unmet dependencies should not be marked "ready."
- Surface blockers early. A task that slips on WD+2 can cascade through the entire close.
- Distinguish between hard dependencies (must complete first) and soft dependencies (should complete first but can work in parallel with risk).
- Track cycle time: compare actual completion day vs. target day to identify process improvement opportunities.
- Include a "lessons learned" note at the end of each close for tasks that consistently slip.
- When reporting status, use RED/YELLOW/GREEN at the task level so leadership can scan quickly.
- Keep the close checklist as a living document; update it each month based on what changed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

