chat-contextlisted

Carries context from one Cowork chat into the next so the user can start a fresh chat without re-explaining anything. Runs in two directions. HANDOFF mode triggers when the user says "hand off this chat," "save chat context," "wrap this chat," "close this chat," "I'm moving to a new chat," "chat handoff," or "write the handoff," and also when the user says the chat has gotten too long or too big to keep working in. RESUME mode triggers when the user says "resume," "resume from handoff," "pick up where we left off," "load chat context," "continue from the last chat," or opens a chat referencing an earlier session. Where files can be written, handoff saves a structured context file and registers it in a master index; otherwise it prints the same structure as a block the user pastes forward. Resume reads whichever form it finds, states what was loaded, then continues the work. Never fires for a request to summarise the chat back to the user in conversation; that gets a summary, not a handoff.
theAnirudhKumar/work-design · ★ 0 · AI & Automation · score 72

Install: claude install-skill theAnirudhKumar/work-design

# Chat Context Long chats get expensive because every new message carries the whole conversation with it. This skill lets the user close a chat and open a fresh one without losing a thing. It writes a structured context file at the end of a session and reads it back at the start of the next one. This skill owns the handoff procedure only. It does not restate rules that live elsewhere. Where a workspace exists, its root `CLAUDE.md` owns routing and preferences, its file-naming rules own placement, and its voice or style guide owns tone. Read those where the steps below point to them, and skip the pointer where the file does not exist. --- ## What this needs **Minimum: nothing.** In a plain chat with no workspace and no file access, handoff prints the context block and the user pastes it into their next chat. That is the whole loop, and it works. **Better with** somewhere to write files. The handoff becomes a saved file with a master index, so handoffs accumulate into a trail instead of living in a paste buffer, and resume can find the right one without the user carrying it. The structure of a handoff is identical either way. Only where it lands changes. --- ## Mode A: Handoff Triggered when the user signals the chat is ending. Do not wait to be asked twice, and do not offer a conversational summary instead. **Two routes.** With file access, the handoff becomes a file and gets an index row: run A1 through A7. Without it, print the Step A3 structure as one markdown bl