Session Handoff

VerifiedSafe

Writes a comprehensive handoff note at the end of a session. Captures work completed, files changed, remaining tasks, and next steps. Use before ending any work session or switching contexts to ensure continuity.

Sby Skills Guide Bot
ProductivityBeginner
3/4/2026
Claude Code
#session-handoff#context-management#documentation#workflow#note-taking

Recommended for

Automated summary

Writes a structured handoff note at the end of a work session so that context carries over to the next session.

Strengths

  • Enforces a clear structure: summary, changed files, verification, remaining tasks, next steps
  • Fixed, predictable output location at `.context/handoff.md`
  • Quality checklist pushes toward specific, actionable notes
  • Provides a shortened format for short sessions

Limitations

  • Limited to Read, Write and Glob tools, so it cannot run commands or tests to actually verify the work
  • Output quality depends entirely on what the agent retained from the session
  • Assumes a companion `/session-start` skill exists to read the note back
When to use it

Use it at the end of any work session, before switching tasks or contexts, or before compacting the conversation.

When not to use it

Avoid relying on it alone for critical work that needs automated verification, since it records rather than validates.

Security analysis

Safe
Quality score85/100

The skill is a pure documentation-writing procedure that only uses Read, Write, and Glob to produce a markdown handoff note at a fixed path (.context/handoff.md). There are no shell commands, network calls, credential access, destructive operations, or attempts to bypass safety controls. Writing a single scoped file is a minimal, legitimate action.

No concerns found

How this analysis is made

Examples

End of feature session
We're stopping here for today. Write a handoff note so I can pick this up tomorrow.
Before context switch
I need to switch to another project now — capture what we did, the files we touched, and what's left in .context/handoff.md.
Quick handoff
Short session, just made a small config fix. Give me a quick handoff with what changed and how to verify it.

name: handoff description: Writes comprehensive handoff note at session end. Captures work done, files changed, remaining tasks, and next steps. Use before ending any work session or switching contexts. allowed-tools: Read, Write, Glob

Handoff

Make work portable across sessions. Write to .context/handoff.md.

When to Use

  • End of every work session
  • Before switching tasks or contexts
  • Before user leaves
  • When compacting context

Process

  1. Gather: What was requested? What did we do? What changed?
  2. Document: Files, agents, decisions, docs updated
  3. Verify: How to confirm the work is correct
  4. Remaining: What's incomplete, issues, blockers
  5. Prepare: What does next session need?

Output Location

Write to: .context/handoff.md

Essential Sections

# Session Handoff — [Date]

## Summary
[2-3 sentences: what was accomplished]

## Work Completed
- [Feature/fix]: [description]

## Files Changed
| File | Change | Description |
|------|--------|-------------|
| path | modified | what changed |

## Verification
[Commands to run, UI to check, tests to execute]

## Remaining
- [ ] [Incomplete task]
- **Issue**: [description + workaround]

## Next Session
1. Run `/session-start`
2. Load [specific docs]
3. Start with [first action]

Quick Handoff (Short Sessions)

# Quick Handoff — [Date]
**Did**: [one sentence]
**Changed**: [file list]
**Verify**: [one command/action]
**Next**: [what to do]

Quality Check

  • [ ] Summary is specific, not vague
  • [ ] All changed files listed
  • [ ] Verification steps are actionable
  • [ ] Remaining work is explicit
  • [ ] Next session can start immediately

Related

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/session-handoff-mmbizjlw/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/session-handoff-mmbizjlw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/session-handoff-mmbizjlw/download' --output '.skill-downloads/session-handoff-mmbizjlw/SKILL.md.part' && mv '.skill-downloads/session-handoff-mmbizjlw/SKILL.md.part' '.skill-downloads/session-handoff-mmbizjlw/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Glob

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/session-handoff-mmbizjlw/SKILL.md' && test -s '.skill-downloads/session-handoff-mmbizjlw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/handoff' && cp -R '.skill-downloads/session-handoff-mmbizjlw' '.claude/skills/handoff'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/session-handoff-mmbizjlw'

openskills read 'session-handoff-mmbizjlw'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/session-handoff-mmbizjlw/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills