How do I install the Handoff skill?

Run npx skillmds@latest add rishbjain1/handoff in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Handoff safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Handoff?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Handoff free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Handoff?

rishbjain1 (@rishbjain1) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Handoff by rishbjain1 — Agent Skill

Name: Handoff
Author: rishbjain1

Handoff

Dump full session state to a persistent memory file in the active project so context can be cleared and any future Claude session restores instantly. Use when user says "handoff", "save context", "dump memory", "clear safely", "remember everything", or before /clear.

rishbjain1 17b9849 2.8 KB Updated Sep 17, 2026

File contents

/handoff — Session State Persistence

When invoked, write a comprehensive memory dump so future Claude sessions can resume w/o losing knowledge.

When to use

User about to /clear and wants knowledge to persist
Context window getting heavy (>50% used)
End of long working session
Before switching projects
After major shipped milestone

What to capture (in this order)

Identity — who user is, contacts, current location/situation
Active project — repo path, stack, deployed URL, recent changes
Roadmap / locked plan — phases, priority order, blockers
Live state snapshots — any numbers or system state the next session must not re-derive
Decisions still open — pending actions, choices waiting on user
User patterns — communication style preferences, tools used, do/don't rules
Resume protocol — exact files to read first when context restored

Where to write

Primary: <repo>/.claude/SESSION_MEMORY.md Secondary (if applicable): append a summary to your long-term notes store Tertiary: insert priority rows into Supabase action_queue (or equivalent task DB) so plan visible on phone/PWA

Output format

Use markdown w/ numbered sections. Heavy use of bold + tables for scannability. End w/ explicit "How to resume from clear context" checklist.

After writing

List files written
Tell user: "Context dumped. Clear safely. Next session reads <path> first."

Suggest the 3-5 line bootstrap message user pastes to next Claude:

Read .claude/SESSION_MEMORY.md before doing anything else.
Then read ROADMAP.md.
Then ask me what to work on.

Auto-trigger conditions

Suggest /handoff proactively when:

Conversation exceeds ~40 turns
User mentions "context", "clear", "remember", "save"
Major work session winding down
Multiple tools loaded but mostly stale

Constraints

Do NOT include secret values (API keys, tokens, passwords). Reference names only.
Do NOT bloat — every line earns its place. Future Claude reads this in one pass.
Do NOT speculate — only document what shipped or what's locked. Speculation = noise.
Mark caveman-mode active/inactive so future session knows tone preference.

Example invocation

User: "context is getting big, save it" You:

Identify active project (recent file edits / cwd)
Pull live state (curl prod endpoints, query DB for current snapshot)
Write SESSION_MEMORY.md w/ everything above
Confirm + provide bootstrap message

---name: handoffdescription: Dump full session state to a persistent memory file in the active project so context can be cleared and any future Claude session restores instantly. Use when user says "handoff", "save context", "dump memory", "clear safely", "remember everything", or before /clear.---# /handoff — Session State PersistenceWhen invoked, write a comprehensive memory dump so future Claude sessions can resume w/o losing knowledge.## When to use- User about to /clear and wants knowledge to persist- Context window getting heavy (>50% used)- End of long working session- Before switching projects- After major shipped milestone## What to capture (in this order)1. **Identity** — who user is, contacts, current location/situation2. **Active project** — repo path, stack, deployed URL, recent changes3. **Roadmap / locked plan** — phases, priority order, blockers4. **Live state snapshots** — any numbers or system state the next session must not re-derive5. **Decisions still open** — pending actions, choices waiting on user6. **User patterns** — communication style preferences, tools used, do/don't rules7. **Resume protocol** — exact files to read first when context restored## Where to write**Primary:** `<repo>/.claude/SESSION_MEMORY.md`**Secondary (if applicable):** append a summary to your long-term notes store**Tertiary:** insert priority rows into Supabase `action_queue` (or equivalent task DB) so plan visible on phone/PWA## Output formatUse markdown w/ numbered sections. Heavy use of bold + tables for scannability. End w/ explicit "How to resume from clear context" checklist.## After writing1. List files written2. Tell user: "Context dumped. Clear safely. Next session reads `<path>` first."3. Suggest the 3-5 line bootstrap message user pastes to next Claude: ``` Read .claude/SESSION_MEMORY.md before doing anything else. Then read ROADMAP.md. Then ask me what to work on. ```## Auto-trigger conditionsSuggest /handoff proactively when:- Conversation exceeds ~40 turns- User mentions "context", "clear", "remember", "save"- Major work session winding down- Multiple tools loaded but mostly stale## Constraints- Do NOT include secret values (API keys, tokens, passwords). Reference names only.- Do NOT bloat — every line earns its place. Future Claude reads this in one pass.- Do NOT speculate — only document what shipped or what's locked. Speculation = noise.- Mark caveman-mode active/inactive so future session knows tone preference.## Example invocationUser: "context is getting big, save it"You:1. Identify active project (recent file edits / cwd)2. Pull live state (curl prod endpoints, query DB for current snapshot)3. Write SESSION_MEMORY.md w/ everything above4. Confirm + provide bootstrap message

Frequently asked questions