Skip to content
Back to skills

Handoff

ASecurity

Compacts the current conversation into a handoff document so a fresh agent can continue the work in a new session.

  • 15 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 26, 2026
ai-agentsbashapi

Works with

  • api

Security analysis

A100/100

Scanned September 26, 2026

npx -y skills add zernie/vigiles --skill handoff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Handoff?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Handoff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zernie-handoff/badge)](https://www.skillsdirectory.com/skills/zernie-handoff)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: handoff
description: >-
  Compacts the current conversation into a handoff document so a fresh agent
  can continue the work in a new session.
disable-model-invocation: true
argument-hint: "What will the next session be used for?"
allowed-tools:
  - Read
  - Grep
  - Glob
  - Write
  - Bash
---

# Handoff

Write a handoff document summarising the current conversation so a fresh agent
can continue the work. Save it to the temporary directory of the user's OS —
not the current workspace.

Include a "suggested skills" section in the document, which suggests skills
that the next agent should invoke.

Do not duplicate content already captured in other artifacts (specs, plans,
ADRs, issues, commits, diffs). Reference them by path or URL instead.

Redact any sensitive information, such as API keys, passwords, or personally
identifiable information.

If the user passed arguments, treat them as a description of what the next
session will focus on and tailor the document accordingly.

## When to Use

- The conversation is long and the work needs to continue in a fresh session
- Handing the current task to another agent (or another person's agent) that
  has no access to this conversation
- Preserving hard-won context — decisions made, dead ends explored, current
  state — before it is lost to context compaction

## When NOT to Use

- The work is finished; write a commit message, PR description, or docs
  instead
- The context is already fully captured in artifacts (a plan file, an issue,
  a spec) — point the next session at those directly

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.