paseo-handoff

Use it when:: You want another agent, from any provider Paseo runs, to take over the task you're working on.
It does:: Picks an agent profile from Paseo's configured profiles, writes a briefing for an agent with zero context, and launches it in your workspace or a new worktree.
You get:: A new agent titled [Handoff] working from that briefing, which Paseo lists among your subagents until you detach it yourself.
Keeps:: The task's intent: an investigate-only task tells the new agent not to edit files, a refactor says refactor, not rewrite.
Needs:: Paseo running with its MCP tools, and the repo's paseo skill.

Needs Paseo running, from its desktop app or the @getpaseo/cli daemon, with its MCP tools. It reads the repo's paseo skill first, which isn't listed, so install it alongside.

TL;DR

Paseo is an open-source app that runs coding agents such as Claude Code and Codex side by side, each in its own worktree. This skill passes your current job to one of them. It first reads Paseo's agent profiles and their notes, then takes the profile you name or the one whose notes best fit the work, falling back to Paseo's list of providers when none fits. The briefing follows a fixed outline: task, context, relevant files, current state, what was tried and why it failed, decisions with their reasons, acceptance criteria and constraints. Say "in a worktree" and it creates an isolated workspace on a short branch named after the task. It then creates the agent with the briefing as its first prompt and tells you which agent and workspace it used. It doesn't wait for the new agent or poll it, and it leaves detaching it from your subagents to you.

Summarizes the skill at 9f68af0.

npx skills add https://github.com/getpaseo/paseo --skill paseo-handoff

skills.sh page Source on GitHub All skills from getpaseo/paseo

Total Downloads: 5,300 on skills.sh, Nov 9, 2026
Repo stars: 23,565 getpaseo/paseo
First seen: Mar 15, 2026 on skills.sh

Weekly Downloads

220

+21% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	182
Sep 28	219
Oct 5	241
Oct 12	207
Oct 19	181
Oct 26	190
Nov 2	213
Nov 9	220

Category	category:agents category:software-engineering Build agents, orchestrate workers and give agents memory. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:command A one-shot action you invoke by name, such as turning the conversation into a PRD.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:cli needs:mcp A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI. Needs an MCP server connected.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	handoff multi-agent
Stack	stack:paseo

SKILL.md

From getpaseo/paseo at 9f68af0. Checked daily, last changed Nov 7, 2026.

Frontmatter

name: paseo-handoff
description: Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.
user-invocable: true

Handoff Skill

Transfer the current task — context, decisions, failed attempts, constraints — to a fresh agent. The receiving agent starts with zero context, so the handoff prompt must be a self-contained briefing.

Use the user's request and current conversation as input, including any arguments supplied with the skill invocation.

Prerequisites

Read the paseo skill. Call list_profiles before choosing the receiving agent. Do not create it until you have read the configured profiles and their notes.

Parsing arguments

Agent profile — explicit profile name first; otherwise choose the profile whose notes best match the work. Materialize it into create_agent as described by the paseo skill. If no profile fits, use Paseo's provider discovery fallback.
Isolation — "in a worktree" / "worktree" → create a workspace with isolation: "worktree", using a short branch name derived from the task.
Task description — anything else the user said.

The handoff prompt

The receiving agent has zero context. Include:

## Task
[Imperative description.]

## Context
[Why this task exists, required context.]

## Relevant files
- `path/to/file.ts` — [what it is and why it matters]

## Current state
[What's done, what works, what doesn't.]

## What was tried
- [Approach] — [why it failed or was abandoned]

## Decisions
- [Decision — rationale]

## Acceptance criteria
- [ ] [Criterion]

## Constraints
- [Must-not / must-preserve]

Preserve task semantics. Investigate-only → "DO NOT edit files." Fix → "implement the fix." Refactor → "refactor, not rewrite." Carry the user's exact intent.

Launch

Prepare the handoff in a dedicated workspace:

Select the current workspace or call create_workspace with the requested isolation.
Call create_agent with a [Handoff] <task> title, the briefing as initial prompt, and the selected workspaceId when explicit placement is needed.
Return the agent and workspace to the user, explaining that it remains in your subagent track until they detach it manually.

Do not encode independence as a create mode and do not invoke CLI or wire-level detach operations. Detach is a user gesture in the subagents track.

Do not wait or poll for the agent to finish.