handoff

Write path-free, clipboard-ready handoff prompts for delegating tasks to another agent.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating a task to another AI agent often produces vague prompts that leak local filesystem paths, skip independent review, or lack the context a fresh agent needs to orient. This Skill writes a standalone, clipboard-ready handoff prompt that gives the receiving agent portable context and clear review-first instructions. ## Core Features & Use Cases - Standalone Prompt Generation: Builds a self-contained prompt with repo/product context, constraints, non-goals, validation expectations, and output shape. - Path-Free Portable Anchors: Replaces filesystem paths with repo owner/name, issue/PR URLs, branch names, symbols, and search terms so the prompt works anywhere. - Review-First Delegation: Instructs the receiving agent to independently verify the task is real, well-scoped, and not already solved before implementing. - Clipboard Integration: Copies the finished prompt via pbcopy, wl-copy, xclip, or clip.exe with safe temp-file handling. - Use Case: You investigated a bug and want a colleague's agent to pick it up—run the handoff to get a complete prompt on your clipboard, ready to paste into a new session. ## Quick Start Ask the agent to write a handoff for the task you want to delegate, for example by saying "handoff the flaky login test investigation".

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I write a handoff prompt for another AI agent?▼

Invoke the handoff skill with a short task label, and it gathers repo, issue, and branch context to write a standalone prompt. The prompt is copied to your clipboard so you can paste it into a fresh agent session.

What should a good agent delegation prompt include?▼

A good delegation prompt includes portable repo and product context, the trigger for the task, constraints and non-goals, validation expectations, and the desired output shape. It should ask the receiving agent to independently review the task before implementing anything.

Why should handoff prompts avoid filesystem paths?▼

Filesystem paths are machine-specific and break when the receiving agent works in a different checkout or environment. Portable anchors like repo owner/name, issue URLs, branch names, and public symbols let any agent locate the right context on its own.

Does the handoff skill work on Linux or Windows clipboard?▼

Yes, it uses pbcopy on macOS and falls back to wl-copy, xclip, or clip.exe on other platforms. If no clipboard tool is available, it prints the prompt and notes that clipboard copy was unavailable.

When should I not use a handoff prompt?▼

Avoid handoffs for trivial tasks you can finish directly, or when you cannot provide enough context for a fresh agent to orient. The skill is meant for delegating substantive investigation or implementation work, not one-line commands.