ad-handoff

Compact an AI session into a portable markdown handoff document in the OS temp directory.

728|16|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ad-handoff
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-handoff
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compact the current AI session into a portable handoff document saved to the OS temporary directory, enabling seamless continuation by another agent.

Core Features & Use Cases

  • Ephemeral handoffs written to the OS temp directory to avoid repository pollution.
  • Captures live state — current branch, open artifacts, unresolved decisions, in-progress diff, recent errors — and references artifacts by path to avoid content duplication.
  • Redacts secrets before writing and enumerates recommended next skills to facilitate handover between agents.
  • Useful during agent handoffs, session wrap-ups, or when switching collaborators to preserve continuity.

Quick Start

Manually trigger a handoff to generate the ephemeral document and pass it to the next agent.

Frequently Asked Questions about ad-handoff

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

FAQPage Schema
How do I hand off an AI session state to another agent without polluting the repository?

To hand off an AI session state, you can generate a portable markdown handoff document in the OS temporary directory. This captures the live session state, references artifacts by path, and avoids committing files to the repository.

What is the best way to preserve conversation continuity when switching AI collaborators?

The best way to preserve conversation continuity is to compact the running session into an ephemeral document. This artifact captures unresolved decisions, open artifacts, and recent errors to facilitate a seamless agent handover.

How does an ephemeral handoff document handle secrets and existing artifacts?

An ephemeral handoff document handles secrets by automatically redacting them before writing to the OS temp directory. It references existing artifacts by their file paths to avoid content duplication while preserving session state.

Can I use this session handoff approach for wrapping up a conversation and recommending next steps?

Yes, you can use this session handoff approach when wrapping up a conversation. The generated document enumerates recommended next skills, lists in-progress diffs, and captures the current branch to guide the subsequent AI agent.

Do I need any dependencies or specific components to trigger an ephemeral AI session handoff?

You do not need any dependencies or specific components to trigger an ephemeral AI session handoff. You can manually trigger the handoff to generate the markdown artifact in the OS temporary directory and pass it to the next agent.