handoff

Generates a session handoff document summarizing work for a context-free agent.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/natthasath/natthasath-marketplace --skill handoff-natthasath
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/natthasath/natthasath-marketplace/tree/main/plugins/session/skills/handoff
Command: npx skills add https://github.com/natthasath/natthasath-marketplace --skill handoff-natthasath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Claude Code session ends, all context disappears, forcing the next session or teammate to re-read the entire transcript. This Skill writes a concise handoff document so a fresh agent with zero context can pick up the work immediately. ## Core Features & Use Cases - Session Summarization: Captures what was done, what decisions were made, and what remains unfinished. - Reference Instead of Duplication: Links to existing specs, plans, ADRs, issues, and commits by path or URL instead of copying content, keeping the document lean and consistent. - Suggested Skills Section: Recommends which skills the next session should invoke based on remaining work. - Automatic Redaction: Strips API keys, passwords, and PII before saving, with no exceptions. - Use Case: Before ending a long debugging session, run /handoff fix the failing auth tests to save a summary to the OS temp directory that a colleague or new session can read to continue immediately. ## Quick Start Ask the assistant to run /handoff with an optional note about what the next session should focus on, then share the saved temp file path with whoever continues the work.

Frequently Asked Questions about handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hand off a Claude Code session to another agent?▼

Invoke /handoff with an optional description of what the next session should focus on. The skill summarizes the conversation, redacts sensitive data, and saves a handoff document to the OS temp directory, then reports the file path.

What is the difference between session-name and handoff skills?▼

session-name runs at the start of a session to set its name and purpose, while handoff runs at the end to summarize outcomes and remaining work. They are complementary bookends of a session lifecycle.

Where is the handoff document saved?▼

The document is saved to the operating system's temp directory: %TEMP% on Windows, $TMPDIR or /tmp on macOS and Linux. It is intentionally not stored in the project folder because it is a transient transfer artifact, not a permanent project file.

Does the handoff skill remove API keys and personal data?▼

Yes, redaction is mandatory and unconditional. Before saving, the skill removes or blanks all sensitive information such as API keys, passwords, and personally identifiable information, even if the user did not request it.

Why does the handoff document reference files instead of copying content?▼

Content already stored in specs, plans, ADRs, issues, or commits is referenced by path or URL rather than duplicated. This prevents the handoff document from bloating and avoids two copies of the same information drifting out of sync.