close-management
/close-management
Plan and control month-end, quarter-end, and year-end close activities. Use for close calendars, dependency management, status tracking, bottleneck escalation, readiness checks, and post-close improvement.
- Author
- rongxinzy ↗
- Repository
- rongxinai ↗
- Licence
- AGPL-3.0
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
What it does and when to use it
Plan and control month-end, quarter-end, and year-end close activities. Use for close calendars, dependency management, status tracking, bottleneck escalation, readiness checks, and post-close improvement.
Original author description
Plan and control month-end, quarter-end, and year-end close activities. Use for close calendars, dependency management, status tracking, bottleneck escalation, readiness checks, and post-close improvement.
How it works
- Build the close plan
- Daily control
- Readiness gates
SKILL.md preview
--- name: close-management description: Plan and control month-end, quarter-end, and year-end close activities. Use for close calendars, dependency management, status tracking, bottleneck escalation, readiness checks, and post-close improvement. --- # Close Management ## Build the close plan Define the close date and work backward through: - data and subledger cut-off; - bank, payroll, billing, payables, inventory, fixed assets, and intercompany close; - recurring and non-recurring entries; - balance-sheet reconciliations; - consolidation, eliminations, currency translation, tax, and reporting; - variance review, controller review, executive sign-off, and lock. Each task needs an ID, entity, process, owner, reviewer, planned start/end, predecessor, required input, evidence, materiality, status, blocker, and completion timestamp. ## Daily control 1. Update status from evidence, not verbal assurance. 2. Identify critical-path delays and quantify downstream impact. 3. Escalate blocked, overdue, high-risk, and material unresolved items. 4. Prevent premature completion where entries, reconciliations, or reviews are pending. 5. Record late adjustments and assess whether the close must reopen. ## Readiness gates - subledgers and interfaces complete; - material entries posted and approved; - key accounts reconciled; - intercompany differences resolved or approved; - statements tie and material variances are explained; - open items are below threshold or formally accepted; - reviewers have signed off and the ledger lock decision is recorded. After close, compare planned vs actual duration, late tasks, late entries, recurring exceptions, and manual effort. Assign improvement actions with owners and due dates.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rongxinzy/rongxinai | 90 | AGPL-3.0 |
| alebgl77/claude-inc | 100 | MIT |
| anthropics/knowledge-work-plugins | 100 | Apache-2.0 |
| GAJETOso/financeskills | 90 | MIT |
| sandbaseai/sandbase-skills | 90 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 072e7a4e1b7d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90close-status
Use when reporting the evidence-backed status of a named month-end or quarter-end close, its blockers, counted completion, and dependency path. Not for explaining budget variances; use variance-analysis. - 90month-end-close
Run or review a month-end close: checklist, reconciliations, accruals, cut-off and sign-off. Use when the user asks to close a month or check close readiness. - 100month-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… - 100run-close-calendar
Runs the month-end or quarter-end close calendar - tasks, owners, dependencies, workday due dates, status from the close tracker, Teams and mail, critical path, overdue and blocked items - and drafts a daily close status note. Reads and reports; never marks tasks complete or… - 90month-end-close-checklist-runner
Run a disciplined month-end close: every task sequenced, evidenced and signed off. TRIGGERS - Use when user needs help with month end close checklist runner related tasks. - 100month-end-close-orchestrator
Guides finance teams through the month-end close process with structured checklists, reconciliation task tracking, journal entry templates, variance analysis with commentary, and close status dashboards. Adapts to the organization's chart of accounts and close calendar. Use when…