handoff

Create handoff documents from conversation summaries with redacted sensitive information.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Matthieusz/skills --skill handoff-matthieusz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/Matthieusz/skills/tree/main/handoff
Command: npx skills add https://github.com/Matthieusz/skills --skill handoff-matthieusz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of passing off conversations to another agent, ensuring that critical information is preserved without repetition and with clear next steps.

Core Features & Use Cases

  • Summarize Conversations: Generate a concise document capturing the essence of the conversation.
  • Suggested Skills: Propose relevant skills to continue the session for the next agent.
  • No Duplication: Reference existing documents like PRDs and issues instead of duplicating content.
  • Redaction: Protect sensitive information from being included in the handoff.

Quick Start

Use the handoff skill to create a handoff document for the 'user onboarding' conversation.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I create a conversation summarization for customer service handoff?

This Skill automates conversation summarization for customer service handoff by generating a concise document that captures essential context, suggests next steps, and redacts sensitive information for the receiving agent.

Can I redact sensitive information when generating an agent handoff document?

Yes, the agent handoff document automatically redacts sensitive information to protect user privacy. It ensures that critical conversation context is preserved without exposing confidential details during the support transition.

What is the best way to transition a support conversation to another agent without losing context?

The best way to transition a support conversation is using an automated handoff document. It summarizes the conversation essence, references existing issues without duplication, and suggests relevant skills to continue the session.

Does the handoff document duplicate existing issues and PRDs during support transition?

No, the handoff document avoids duplication during support transition. It references existing documents like PRDs and issues directly instead of copying their content, ensuring the receiving agent gets context without redundant information.

How do I suggest relevant skills for the next agent during a support handoff?

To suggest relevant skills during a support handoff, this Skill analyzes the conversation summary and proposes appropriate skills to continue the session, helping the next agent pick up the workflow seamlessly.