Skip to content
Skills Library
AI & agents · Writing

save

/save

Write a handoff document that lets a fresh Claude session (cold context, any model) continue the current work. Captures the mission, the user's latest request verbatim, state, decisions, dead ends, constraints, open questions and exact next steps, plus git state read from the repo. Optionally commits and pushes first, or puts the file in the repo so another account or machine can pull it. Use when the user says "handoff", "hand off", "save progress", "wrap up this session", "I'm running out of context", "pass this to a new session", or types /handoff:save.

Repository
handoff ↗
Licence
MIT
Last repository change
07.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write a handoff document that lets a fresh Claude session (cold context, any model) continue the current work. Captures the mission, the user's latest request verbatim, state, decisions, dead ends, constraints, open questions and exact next steps, plus git state read from the repo. Optionally commits and pushes first, or puts the file in the repo so another account or machine can pull it. Use when the user says "handoff", "hand off", "save progress", "wrap up this session", "I'm running out of context", "pass this to a new session", or types /handoff:save.

Triggers from the description

handoffhand offsave progresswrap up this sessionm running out of contextpass this to a new session

Arguments

/save [topic: slug] [repo] [commit] [push] [focus text]
Original author description

Write a handoff document that lets a fresh Claude session (cold context, any model) continue the current work. Captures the mission, the user's latest request verbatim, state, decisions, dead ends, constraints, open questions and exact next steps, plus git state read from the repo. Optionally commits and pushes first, or puts the file in the repo so another account or machine can pull it. Use when the user says "handoff", "hand off", "save progress", "wrap up this session", "I'm running out of context", "pass this to a new session", or types /handoff:save.

How it works

  1. Steps
  2. Rules
Original SKILL.md headings · 46 lines, 581 words
SKILL.md preview
---
name: save
description: Write a handoff document that lets a fresh Claude session (cold context, any model) continue the current work. Captures the mission, the user's latest request verbatim, state, decisions, dead ends, constraints, open questions and exact next steps, plus git state read from the repo. Optionally commits and pushes first, or puts the file in the repo so another account or machine can pull it. Use when the user says "handoff", "hand off", "save progress", "wrap up this session", "I'm running out of context", "pass this to a new session", or types /handoff:save.
when_to_use: The context window is filling (about 70-80%), the user is stopping for the day, or work should move to another session, account, machine or agent. To also start the new session, use /handoff:new. To resume, use /handoff:pickup.
argument-hint: "[topic: slug] [repo] [commit] [push] [focus text]"
---

# /handoff:save

Write one file a different agent can act on with no memory of this session. Optimise it for a machine reader: dense, specific, absolute paths, no narrative.

Arguments: $ARGUMENTS
Session id: `${CLAUDE_SESSION_ID}` (if this still reads as a literal placeholder, the id is unknown; pass nothing).

## Steps

1. **Parse the arguments.**
   - `topic: slug` names the file. Otherwise derive a 2-4 word slug from the work.
   - `repo` writes into `<repo>/.claude/handoffs/` so the file travels with git (another account, machine or teammate). Default is the private user store `~/.claude/handoffs/<project>/`.
   - `commit` / `push` allow the script to stage everything, commit `wip: handoff - ...` and push. Without them nothing is committed or pushed. If `repo` is set and the tree is dirty, ask once (choice question: commit and push, commit only, neither) because the other side only sees what is pushed.
   - Anything else is a focus: weight the document towards it.

2. **Collect facts** (read-only, nothing committed yet):
   ```
   node "${CLAUDE_PLUGIN_ROOT}/scripts/collect-state.mjs" --session "${CLAUDE_SESSION_ID}" --topic <slug> [--repo]
   ```
   It prints JSON: project, branch, head, ahead/behind, dirty files, recent commits, detected commands, transcript path and `file_path` (where to write). An unsubstituted session placeholder is ignored (session_id becomes "unknown"). Do not run git by hand to repeat it.

3. **Gather the rest from the conversation**, not from tool output: the goal, the user's latest request word for word, every instruction or prohibition the user gave, what is done, what is half done, what was tried and failed, decisions with reasons, what is waiting on the user, how to verify.

4. **Route durable knowledge elsewhere.** Facts that stay true across sessions (conventions, architecture, build workflow) belong in the project's memory or CLAUDE.md. If the project has a memory index, save new durable facts there and leave a one-line pointer in the handoff. The handoff holds transient state only.

5. **Write the file** to `file_path` using `${CLAUDE_SKILL_DIR}/template.md`. Keep every section header; write `(none)` for an empty one so the reader knows it was considered. Fill the frontmatter from the script output.

6. **Privacy check.** Re-read what you wrote. Never include secret values (tokens, passwords, keys, private URLs with credentials, personal data the task does not need). Write the name of the secret and where it lives instead. List what you left out by name in `sensitive_items`.

7. **Commit and push, only if step 1 allowed it** (so the handoff file is in the commit in `repo` mode):
   ```
   node "${CLAUDE_PLUGIN_ROOT}/scripts/collect-state.mjs" --check --commit "handoff: <topic>" [--push]
   ```
   Then edit the file's "3 State" Git line with the printed `push_status`, `head` and `committed` values. In `repo` mode with `push`, the file edit itself stays uncommitted; that is fine, the pushed copy already says the commit hash. Never force-push.

8. **Report in at most five lines:** the file path, topic, branch and push status, the top 2-3 next actions, and how to resume: `/handoff:pickup <path>` in any new session, or `claude "/handoff:pickup <path>"` from a shell. Do not replay the document.

## Rules

- Hand off early. The writing needs headroom; do it at 70-80% context, not at the limit.
- Never force-push or switch branches. Stay on the current branch.
- Next actions must name files, functions and commands. "Continue the refactor" is useless; "finish `parseConfig` in `src/config.ts:40`, then run `npm test -- config`" is not.
- Record hypotheses you already ruled out. They save the next session the most time.
- Quote the user for requests and constraints; paraphrase only your own conclusions.
Files in this package (2)
  • SKILL.md 5 KB
  • template.md 3 KB

Versions

RepositoryScoreLicence
This page · NourEldinShobier/handoff100MIT
nigelng/nng-kit100MIT
erayozenn/BigHead-2ndBrain100MIT
agricidaniel/claude-obsidian100MIT
arcfjmt/handoff100MIT
ryanonline1234/smart-compact100MIT
xtsoftwarelabs/neatcontext-plugins100MIT
ARCASSystems/FounderOS90MIT
adb-software-solutions/contextbrain-plugins82MIT

Database snapshot: 13.11.2026 · package version 0f10a30b79d6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90handoff
    Write a handoff document so another agent or a fresh session can continue this work. Use for "handoff", "hand this off", "write a handoff", "continue this in a new session" or "pass this to another agent". For deciding whether to compact or clear, use session-budget.
  • 90handoff
    Write a structured session handoff so a fresh session resumes losslessly. Use when context is filling up (around half the window), when wrapping a work session, or when the user says "handoff", "checkpoint", "wrap up", or "save state".
  • 100session-handoff
    Write an agent session handoff: state, decisions, unfinished work, checks, next steps. Use for "hand this off" or a context window running out.
  • 100handoff
    Write a compact handoff document so a fresh agent, thread, or session can continue. Use when context is long, the user wants to switch threads, work must be paused, or the agent needs to summarize current state without duplicating existing docs or diffs.
  • 85handoff
    Compact the current conversation into a handoff document for another agent to pick up. Use when the user says "hand this off", "wrap up", "save context", "continue later", "pass this to another session", "I need to stop here", "pick this up later", or when a session is ending…
  • 100session-handoff
    Write or update handoff.md so the next agent, starting with a fresh context, can continue this work - the goal, the progress, what worked, what did not, and the next steps. The file stays out of git. Use when the user wants to hand the work over, end the session, or continue in a clean context.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.