monthly-checkpoint
Installation
SKILL.md
Monthly checkpoint
A new habit or data source feels useful in week one. A month later, nobody knows if it still pays off. Run one honest review, then decide: keep, change, or stop.
When to use
- About 30 days after the owner turns on something new: meeting recordings, a daily digest, an inbox rule, a new tracker, a routine you run for them.
- When the owner asks "is this still worth it?" or "what did we get from X?"
- Before you expand a new setup (more sources, more people, more automation).
Skip it if there is less than about two weeks of data. Offer to run it later instead.
What to gather
Look at the real record for the period, not your memory of it.
- Captured: how many items came in (recordings, notes, digests, tickets). Note the date range.
- Used: how many items fed something downstream: a reply, a decision, a task, a doc, a follow-up. Count them. Name two or three concrete examples.
- Ignored: items that were captured and never opened, cited, or acted on.
- Silent failures: gaps in the dates, broken syncs, expired auth, empty or truncated items, things captured but never surfaced to the owner, alerts that fired and went nowhere.
- Cost: time the owner spent on it, noise it created, and any privacy or sharing risk.
- Owner signal: what the owner said about it during the month, including complaints and things they asked for twice.