mcpField
C
claude-handoff

claude-handoff

github.com/tt-a1iAgent workflows19298 installsUpdated 2d ago
Repository

About claude-handoff

A skill that prepares a conversation handoff for a fresh Claude agent, saves it in the OS temporary directory, and starts the agent with that summary as its prompt. It includes guidance for naming the agent, avoiding duplicate artifacts, redacting sensitive data, and tailoring the handoff to passed arguments.

Key features

  1. 01Summarizes conversation state
  2. 02Saves summary in temporary directory
  3. 03Starts a background Claude agent
  4. 04Includes suggested skills
  5. 05Redacts sensitive information

Use cases

  1. 01Continuing work in a fresh agent session
  2. 02Passing a focused task to a background agent

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tt-a1i/matt-skills-with-to-goal --skill claude-handoff

After installing, type/claude-handoffin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Write a handoff summary of the current conversation so a fresh agent can continue the work. Save it to the temporary directory of the user's OS, then launch a background agent seeded with it as its prompt: claude --bg --name "<descriptive name>" -- "$(cat <summary file>)". Passing the file keeps the shell from running backticks or expanding $ in the 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.

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

Comments

Markdown supported