How do I install the Session Handoff skill?

Run npx skillmds@latest add hsinhan-h/session-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 Session 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 Session 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 Session Handoff free to use?

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

Who published Session Handoff?

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

Session Handoff by hsinhan-h — Agent Skill

Name: Session Handoff
Author: hsinhan-h

Session Handoff

Compact the current conversation into a handoff document for another agent to pick up, saved at the project root and copied to the clipboard. Use when the user wants to end a session and hand off context to a fresh agent/session.

hsinhan-h 7d02ab5 2.0 KB Updated Sep 17, 2026

File contents

Write a handoff document summarising the current conversation so a fresh agent can continue the work.

Where to save

Save the document at the project root directory — not a temp/scratchpad directory:

Determine the project root with git rev-parse --show-toplevel.
If that fails (not a git repo), fall back to the current working directory.
Save the file directly there — do not create a handoff/ subfolder unless one already exists.

Filename

Format: handoff-YYYY-mm-dd_HHmm-<topic-slug>.md

YYYY-mm-dd_HHmm — current local date and time, 24-hour, no colons/seconds (e.g. 2026-07-02_1430).
<topic-slug> — 2-4 English kebab-case words in <scope>-<topic> shape, e.g. auth-flow-refactor (scope: auth, topic: flow-refactor) or payment-timeout-debug (scope: payment, topic: timeout-debug). Keep it short and specific — this is what makes the file distinguishable once several handoffs pile up in the same folder.

Example: handoff-2026-07-02_1430-auth-flow-refactor.md

Content

Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.

Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

Redact any sensitive information, such as API keys, passwords, or personally identifiable information.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

After saving

Copy the full contents of the saved file to the clipboard so the user can paste it straight into the next session:

Get-Content -Raw <path> | Set-Clipboard

Confirm to the user that the file was saved (state the path) and that its contents were copied to the clipboard.

---name: session-handoffdescription: Compact the current conversation into a handoff document for another agent to pick up, saved at the project root and copied to the clipboard. Use when the user wants to end a session and hand off context to a fresh agent/session.---Write a handoff document summarising the current conversation so a fresh agent can continue the work.## Where to saveSave the document at the **project root directory** — not a temp/scratchpad directory:- Determine the project root with `git rev-parse --show-toplevel`.- If that fails (not a git repo), fall back to the current working directory.- Save the file directly there — do not create a `handoff/` subfolder unless one already exists.## FilenameFormat: `handoff-YYYY-mm-dd_HHmm-<topic-slug>.md`- `YYYY-mm-dd_HHmm` — current local date and time, 24-hour, no colons/seconds (e.g. `2026-07-02_1430`).- `<topic-slug>` — 2-4 English kebab-case words in `<scope>-<topic>` shape, e.g. `auth-flow-refactor` (scope: auth, topic: flow-refactor) or `payment-timeout-debug` (scope: payment, topic: timeout-debug). Keep it short and specific — this is what makes the file distinguishable once several handoffs pile up in the same folder.Example: `handoff-2026-07-02_1430-auth-flow-refactor.md`## ContentInclude a "suggested skills" section in the document, which suggests skills that the agent should invoke.Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.Redact any sensitive information, such as API keys, passwords, or personally identifiable information.If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.## After savingCopy the full contents of the saved file to the clipboard so the user can paste it straight into the next session:```powershellGet-Content -Raw <path> | Set-Clipboard```Confirm to the user that the file was saved (state the path) and that its contents were copied to the clipboard.

Frequently asked questions