handoff

Compress the current conversation into a handoff document with redacted PII and artifact references.

228|68|Updated Sep 27, 2023
One-click install
npx skills add https://github.com/SwitchbackTech/compass-calendar --skill handoff-switchbacktech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/SwitchbackTech/compass-calendar/tree/main/.agents/skills/handoff
Command: npx skills add https://github.com/SwitchbackTech/compass-calendar --skill handoff-switchbacktech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compact the current conversation into a concise handoff document for another agent to continue the work.

Core Features & Use Cases

  • Structured handoff: Captures conversation context, decisions, and next steps for a smooth transition to the next agent.
  • Redaction & referencing: Automatically redacts PII and references artifacts by path or URL for traceability.
  • Guided handoff prompts: Includes a "suggested skills" section to guide the next agent's actions; saves to the user's temporary directory.

Quick Start

Generate a concise handoff document summarizing the current conversation for the next agent.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I summarize a conversation for another agent to pick up?

It compresses the current conversation into a concise handoff document, capturing context, decisions, and next steps to ensure smooth knowledge transfer for the next agent.

Does the handoff document redact sensitive information before sharing?

Yes, the handoff document automatically redacts sensitive PII during generation and references external artifacts by path or URL to ensure secure knowledge transfer.

Can I guide the next agent's actions within the generated handoff document?

Yes, you can guide the next agent because the handoff document includes a suggested skills section that provides prompts for the receiving agent to invoke during continuation.

What is the best way to maintain continuity across different agent sessions?

The best way to maintain continuity is to generate a structured handoff document that captures the conversation context and suggests next actions for the incoming agent.

Where does the generated handoff document get saved?

The generated handoff document is saved directly to the user's temporary directory, allowing the next agent to easily access and read the compressed conversation context.