Weekly State of the Mind

Once a week, I run /state-of-brain. Claude reads across the vault, finds the patterns I’ve missed, and writes a synthesis report. It’s one of those features that sounded gimmicky until I actually used it.

What It Does

The skill scans 01 Atlas/, 02 Calendar/, and 03 Efforts/ — not all of them individually, but via the _index.md files first (fast), then drilling into recently modified notes for detail.

It generates a report with four sections:

Emergent Themes — clusters of notes that share tags or overlapping concepts, ranked by recency and density. The interesting ones are themes that suddenly appear across multiple notes that weren’t connected before. Something I captured in Inbox, refined in Atlas, and started building in Efforts — the report surfaces that they’re all the same idea.

Contradiction Detection — notes referencing similar topics with conflicting claims. Particularly useful for time-bound information: pricing that’s changed, a strategy I revised, a rule I updated. Without this, I’d occasionally find two notes giving contradictory advice on the same thing and have no idea which was current.

Stale Knowledge — 03 Efforts/ notes that haven’t been touched in 30+ days. For each one, Claude recommends: archive to Atlas (knowledge has crystallised), delete (abandoned with no useful insights), or reactivate (still relevant given current themes).

Vault Activity — simple counts: notes added, notes refined, indexes updated. Useful mostly for understanding how the system is actually being used versus how I think it’s being used.

Output Location

Reports land at:

02 Calendar/2026/[Month]/Weekly Report/[Month]_Week_N.md

Where N is the week-of-month (1–4), calculated as min(4, ceil(day / 7)).

So for May 15–21, 2026: 02 Calendar/2026/May/Weekly Report/May_Week_3.md.

Design note — Overview.md as the month’s entry point. Each month has an Overview.md that lists daily events and links to its weekly reports. When a new report is written, /organize-calendar appends it to the Overview’s Weekly Reports section automatically. So the Overview is always a complete index of the month — daily entries on top, weekly syntheses below.

Why It’s Actually Useful

The vault is a tool for thinking. But it accumulates knowledge silently — notes connect to other notes, themes develop across weeks, and individual sessions are too focused to notice the bigger patterns.

The weekly report forces a moment of reflection that I wouldn’t otherwise take. Reading that three unconnected notes from the past week all reference the same underlying concept — I genuinely wouldn’t have noticed that day-to-day.

The stale efforts section is the part I use most. Left alone, 03 Efforts/ fills up with active-project notes from two months ago that are now done, abandoned, or graduated into evergreen knowledge. The report flags them and tells me what to do.

It’s weirdly useful. Patterns surface that I’d never notice day-to-day when I’m heads-down in individual notes.

How It’s Triggered

/state-of-brain runs standalone, or as the final phase of /organize-calendar. Since calendar organization is a natural checkpoint (it’s already reading across dated notes), it makes sense to attach the weekly synthesis there.

Running it at the end of /organize-calendar means the indexes are already up to date when the report generates — so it’s reading an accurate map, not stale data.

---

Related: Organizing my Vault — how /organize-calendar fits into the broader pipeline.