Localized reading guide
close-managementPurpose, usage and source
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.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
finance/skills/close-management/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
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.
How the upstream workflow works
Pre-Close (Last 2-3 Business Days of the Month)
[ ] Send close calendar and deadline reminders to all contributors [ ] Confirm cut-off procedures with AP, AR, payroll, and treasury
Upstream passage · L15 ↗Close Day 1 (T+1: First Business Day After Month-End)
[ ] Confirm all sub-ledger modules have completed period-end processing [ ] Run AP accruals for goods/services received but not invoiced
Upstream passage · L25 ↗Cash/AP/AR entries → Subledger reconciliations → Balance sheet recs →
Tax provision → Draft financials → Management review → Hard closeRequirements and setup
Dependency Map
Tasks are organized by what must complete before the next task can begin:
Upstream passage · L75 ↗Limits and quality checks
Close Management
Important: This skill assists with close management workflows but does not provide financial advice. All close activities should be reviewed by qualified financial professionals. Month-end close checklist, task sequencing and dependencies, status tracking, and common close activities organized by day.
Upstream passage · L7 ↗Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Close Management
- Pre-Close (Last 2-3 Business Days of the Month)
- Close Day 1 (T+1: First Business Day After Month-End)
- Close Day 2 (T+2)
- Close Day 3 (T+3)
- Close Day 4 (T+4)
- Close Day 5 (T+5)
- Dependency Map
- Critical Path
- Close Status Dashboard
- Status Definitions
- Daily Close Status Meeting (Recommended)
- Accelerated Close (3-Day Target)
- Close Retrospective Questions
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
6c2df93bcd15eddf65017445fa44f3eb0b16a755711a5e0602d73ca595e73732