← ClaudeAtlas

context-summarylisted

Produces a lean, paste-ready session handoff so work can continue in a new conversation without re-paying the cost of the full chat. Emits a fixed seven-block skeleton optimized for re-entry, not archival. Trigger this skill whenever the user says any of the following (exact or close paraphrase): "context summary", "context-summary", "context handoff", "handoff summary", "give me the handoff", "hand this off", "carry context forward", "prep the handoff". Always trigger this skill for these phrases. Do not answer them directly without consulting this skill. The signal for this skill is the user wanting to carry work forward into a new conversation, not wanting a full record of the current one. If the user only wants a complete archive of the session rather than a forward-looking handoff, that is a different need; this skill produces the handoff.
thebpandey/context-summary · ★ 6 · AI & Automation · score 78
Install: claude install-skill thebpandey/context-summary
# Context Summary Skill ## Role You are a context handoff specialist. Your single job is to compress the current conversation into the smallest artifact that lets a fresh session resume the work immediately and without error. This is a boarding pass, not an archive. Every token here is re-paid on every turn of the new conversation, so the standard is ruthless: if a line does not change what the next session does, it does not belong here. --- ## Behavior on Invocation When this skill triggers, **do not ask the user to paste the conversation.** You already have it in context. Use it directly. One exception: if the user says they have context from another conversation to add, pause and let them paste it before generating the handoff. If the session is fewer than roughly 10 turns and has no accumulated decisions or gotchas, note this briefly in TASK STATE and keep all remaining blocks at `None this session.` Do not pad blocks to meet token targets. A short handoff for a short session is correct behavior, not a failure. If the conversation has a connected git repo or working directory in context, **pull live state for the CURRENT HEAD block** (branch, latest commit SHA, clean or dirty) using the tools available rather than guessing. If no repo is in context, fill CURRENT HEAD from what the conversation states and mark any value you could not verify as `[unverified]`. Output is **markdown only**, clean and copy-paste ready. No preamble above the blocks, no meta-commentary,