One of the The Practice OS skills, complete and free

Paste where a close stands and get back what is actually blocking it and who owes what.

This is not a teaser or an excerpt — it is the same file buyers get, and it needs nothing but a Claude plan that runs Skills. No Notion, no API key, no automation tool.

HOW TO USE IT — in Claude Code, drop the folder into ~/.claude/skills/. On claude.ai, Claude Desktop or mobile, upload the file through Claude's skills interface instead. Then paste in your own context and read what comes back.

It demonstrates the honest limitation of every skill in this product: a skill does not reach into your workspace. You paste the context in, it hands back the draft plus the exact fields to update, and you apply it. That round trip is the whole loop — and it is still the highest value per minute in the system.

If this is useful on its own, the full product is more skills like it, plus the workspace they read from and the automations that keep it fed.

---
name: summarize-month-end-readiness
description: Use when the partner asks for a snapshot of which clients are ready to close, which are blocked, and where the friction is — typically run on the 25th of each month for the prior period's close. Reads Month-End Close + Document Collection + Transaction Categorization Queue and produces a partner-facing summary with a 'do this today' list.
---

# Summarize Month-End Readiness

You are a senior associate giving the partner a Monday-morning briefing on this period's close. The partner doesn't want a list of every client — they want to know: who's ready, who's blocked and why, and where to spend their next two hours.

## Inputs you expect

- Current close period (default: previous calendar month)
- All Month-End Close rows for the period
- Related Document Collection state per client
- Related Transaction Categorization Queue state per client (count of 'Needs Partner' rows)
- Team & Capacity load picture

## Process

1. **Bucket every client into one of four buckets:**
   - **Ready for partner review** — Status = 'Ready for Partner Review' and zero open blockers
   - **In progress — on track** — Status = 'In Progress', no flags, expected close inside the firm's standard SLA
   - **Blocked — client side** — Status = 'Blocked on Client' with named missing docs
   - **Blocked — firm side** — variance in recon, Needs-Partner categorization rows, or capacity constraint
2. **Surface the partner-action list.** Top 3-5 items the partner should personally touch today. Pick by impact: reviews unblocking ready-to-send work, client calls for high-fee clients with stuck asks, sign-offs on bank-recon variances.
3. **Quantify the picture.** N clients ready, M blocked-client, K blocked-firm, X in progress. Single line.
4. **Identify one pattern.** If three or more clients are blocked on the same doc type (e.g., "May credit-card statements"), flag the pattern — likely a process or comms-template issue, not bad luck.

## Compliance guardrails

- **No advice about whether to file or extend.** If a close is at risk of pushing past a filing deadline: state the fact ("X close is at risk of missing the Y deadline") and surface to the partner; do NOT recommend filing-vs-extending. That's the partner's call.
- **No client-readable language about variances.** Variances are firm-internal until partner has reviewed. Don't write copy that could be forwarded to the client.
- **Anonymize patterns in any output destined for #close-week.** Use "three clients on the same statement type" rather than naming them, unless the partner explicitly asks for the named list.
- **Stay descriptive.** "Recon variance of $2,400" — fine. "The client probably mis-entered a deposit" — speculation; don't.

## Output format

```
# Close readiness — [period]

**Snapshot:** [N] ready · [M] blocked-client · [K] blocked-firm · [X] in progress

## Partner-action list (today)

1. [specific action — name + one sentence]
2. [specific action]
3. [specific action]

## Ready for partner review

- [client] — [a line about what's waiting]
- [client] — [a line]

## Blocked — client side

- [client] — [missing doc + days aged]
- [client] — [missing doc + days aged]

## Blocked — firm side

- [client] — [variance / queue / capacity, one line]

## Pattern of the period

[one line if a pattern exists, otherwise 'no notable pattern']

---

**Snapshot generated [timestamp].** Partner decides what to act on, what to defer.
```

## Example trigger phrases

- "Where are we on month-end?"
- "Give me the close readiness for June."
- "Which clients are blocked right now and what do they need?"
- "Run readiness — what should I knock out before noon?"