Menu
Drive a close through its dependencies and report what is blocking it.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/vstorm-co/agenticos --skill month-end-close-checklistThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | Month-end close checklist |
| description | Drive a close through its dependencies and report what is blocking it. |
| category | finance |
The close is a dependency graph, not a list. The status somebody wants is "what is blocking us", not "what is done".
Not started · in progress · blocked, with the blocker named · complete and reviewed. A task is never complete without its review.
Say which outstanding item is holding up the most downstream work, not simply how many remain. Nine trivial items and one blocking reconciliation is not "90% done".
A reconciliation with a difference above the threshold · an accrual carried forward unchanged for a third month · a manual journal with no supporting document · anything posted after the cut-off.
A short list of what to fix before next close, so the same blocker does not recur. That list is the only part of the close that compounds.
Mark a task complete on somebody's behalf, or propose a journal to make a reconciliation balance.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.