Skip to content
Back to skills

Claude Handoff

ASecurity

Hand the current conversation off to a fresh background agent that picks up the work immediately.

  • 382 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 7, 2026
ai-agentsapi

Works with

  • terminal
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 7, 2026

npx -y skills add Asymmetric-al/core --skill claude-handoff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Claude Handoff?

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

Security grade badge for Claude Handoff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/asymmetric-al-claude-handoff/badge)](https://www.skillsdirectory.com/skills/asymmetric-al-claude-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: claude-handoff
description: Hand the current conversation off to a fresh background agent that picks up the work immediately.
argument-hint: "What will the next session be used for?"
disable-model-invocation: true
---

Write a handoff summary of the current conversation so a fresh agent can continue the work. Instead of saving it, launch a background agent seeded with the summary as its prompt: `claude --bg --name "<descriptive name>" "<handoff summary>"`. It starts in the current working directory and returns immediately; the user manages it with `claude agents`.

Always pass `-n`/`--name` with a descriptive name (e.g. `--name "Fix login bug"`); it sets the display name shown in the job list, session picker, and terminal title.

Include a "suggested skills" section in the summary, naming which skills the next agent should call the Skill tool for.

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, since the summary becomes the agent's prompt. <!-- pragma: allowlist secret -->

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

Files in this skill

  • SKILL.md1.3 KB
  • agents/openai.yaml141 B

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…