Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Handoff — Verified Session Knowledge Transfer

    1

    Verified knowledge transfer between Claude Code sessions. Prevent context loss with source-backed questions, grading, and documentation repair.

    Free

    1 useSecurity scanned
    Handoff — Verified Session Knowledge Transfer

    Handoff — Verified Session Knowledge Transfer

    Example session with this skill installed

    /handoff pack → /handoff unpack → /handoff check

    • Read your context and instructions
    • Compiled the handoff

    Verified Session Handoff — Example Output

    Handoff preparation completed.

    The outgoing Claude Code session has consolidated the project context, documented critical decisions and blockers, and generated verification questions for the incoming session.

    Generated Artifacts

    FilePurposeStatus
    .planning/handoff/RESUME-HERE.mdProject state, decisions, constraints, and next stepsCreated
    .planning/handoff/INTERVIEW.mdQuestions testing critical project knowledgeCreated
    .planning/handoff/ANSWERS.mdSource-backed answers from the incoming sessionCompleted
    .planning/handoff/FEEDBACK.mdEvaluation results and required correctionsCompleted

    Knowledge Verification

    QuestionVerdict
    What architectural decision governs the authentication flow?PASS
    Why was the previous caching strategy rejected?PASS
    Which regression tests must run before deployment?DOC-GAP
    What is the next implementation task?PASS
    Which configuration must remain unchanged?PASS

    Verification result: Documentation gap detected.

    The outgoing session identified missing regression-test information, repaired the relevant project documentation, and requested verification of the corrected information.

    Final Verification

    All required questions have been successfully resolved.

    STATUS: GREEN — Knowledge transfer verified.

    The incoming session can now continue development with verified project context. The outgoing session may be closed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Context loss between long-running Claude Code sessions can lead to repeated work, forgotten decisions, and incorrect assumptions. Handoff provides a structured, verifiable knowledge-transfer protocol between two Claude Code sessions running side by side. Instead of assuming the new session understands the project, it tests that understanding before work resumes.

    What it does

    • State consolidation captures critical project decisions, constraints, blockers, and next steps in a structured handoff document.
    • Knowledge interviewing generates targeted questions from the outgoing session's active context.
    • Source-backed answers require the incoming session to cite project documentation or explicitly acknowledge missing information.
    • Automated grading evaluates answers against the outgoing session's knowledge, identifying misunderstandings, missing information, and outdated documentation.
    • Documentation repair corrects identified documentation gaps and inaccuracies before the handoff is approved.
    • Versioned handoffs commits handoff artifacts using Git, providing a traceable record of the process.

    How it works

    1. Pack — Run /handoff pack in the outgoing session to prepare the handoff document and interview.
    2. Unpack — Run /handoff unpack in a fresh session to read the specified documentation and answer the interview.
    3. Check — Run /handoff check in the original session to evaluate answers, repair documentation when necessary, and determine whether the transfer is complete.

    Frameworks & tools

    Designed specifically for Claude Code. Requires Git and two concurrent Claude Code sessions with access to the same project directory.

    Why this beats prompting it yourself

    Traditional session handoffs rely on summaries and assume the receiving agent has understood them. Handoff introduces an explicit verification loop: the outgoing session examines the incoming session's understanding while its original context is still available.

    Unlike passive summaries, Handoff can identify misunderstandings and documentation defects before they propagate into subsequent work.

    Use cases

    • Continuing complex software development across Claude Code sessions.
    • Preserving critical decisions and constraints during context-window transitions.
    • Reducing repeated investigation and incorrect assumptions in long-running projects.
    • Detecting stale or incomplete project documentation during session transitions.

    Known limitations

    Handoff evaluates only the knowledge covered by its generated questions. Verification depends on the outgoing session's remaining context and is not an independent guarantee of correctness.

    Both sessions must remain available until verification completes, and the outgoing session must not be cleared before grading. Git is required for versioned handoff artifacts.

    Requires Git and shared filesystem access between sessions. Does not support third-party state persistence outside of the local repo.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    File Scopes

    **/*.md
    **/*

    Requires local file read/write access to project documentation and handoff artifacts. Uses Git to create local commits. May correct outdated project documentation. Does not push changes or require network access.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill eliminates context loss and hallucinations that occur when starting a fresh session. It uses a structured "interview" and "grading" system to ensure the new agent actually understands the logic and intent of the previous session before work resumes.

    The skill is purpose-built for the Claude Code CLI. It relies on local filesystem access and Git for state tracking, making it ideal for developers working in terminal-based agent environments.

    No, this skill is designed to work within your existing local repository. It uses Git to version the handoff state, allowing you to audit the knowledge transfer through your standard version control history.

    You receive the full skill package for Claude Code, including the commands for state packing, interviewing, and automated grading. This includes all necessary logic to bundle context and verify the alignment of the incoming session.

    Yes, the protocol works seamlessly when switching models. It is actually a primary use case, allowing you to move from a faster model for boilerplate to a more reasoning-heavy model for complex debugging without losing progress.

    Both Claude sessions must have access to the same local filesystem or Git repository. This ensures the 'unpack' command can read the state files and interview questions generated by the 'pack' command.

    New in Agents & Orchestration