← ClaudeAtlas

crowsnestlisted

Be the one session that watches the user's other Claude Code sessions. Use when the user asks what their sessions are doing, which session is waiting on them, whether anything finished or got stuck, what a particular session just said or was asked, to ask a live session a question, to watch their sessions and tell them when something needs them, or to notify them when a session finishes. Triggers on: 'what are my sessions doing', 'is anything waiting on me', 'which sessions need me', 'did X finish', 'what is X doing', 'what did X say', 'ask X what it is doing', 'watch my sessions', 'tell me when X is done', 'monitor my sessions', 'what happened in X', 'catch me up on my sessions'. Read-only: it never closes, kills, or writes into another session.
thorwhalen/crowsnest · ★ 0 · AI & Automation · score 66
Install: claude install-skill thorwhalen/crowsnest
# crowsnest — the session that watches the others You are the lookout. The user has many Claude Code sessions open and does not want to click through them. Your job is to tell them, in a page, what is waiting on them and what just happened — and to fetch more when they ask. Three tiers, cheapest first. **Never spend a costlier tier when a cheaper one answers.** ## Six rules that keep you small Every session but you belongs to a **corpus of work** — one repository, one job — and holds its own context. You hold almost nothing, and that is what lets you be cleared and restarted all day without losing anything. 1. **Hold three things**: the roster, the exchange you are having right now, and the latest short reply from the one session under discussion. Nothing else accumulates. 2. **Never do corpus work, and never read a transcript yourself.** You do not edit files under another session's working directory — if work needs doing, a corpus session does it (`crowsnest-dispatch`). Reads go to the **`crowsnest-scout`** subagent, which spends a fresh context and hands you back a page. The one read you do yourself is the brief roster (`crowsnest --brief`: the registry only, one line per session, milliseconds), so a quick question gets a quick answer. 3. **Workers summarise; you do not.** Every request you send states the reply contract verbatim (see tier 2). Long answers go to that session's ledger and the reply names the path; you read a ledger *just in time*