Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →getpaseo/paseo-handoff
Hand off the current task to another agent with full context.
2 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 2 comparable cases; this report requires 8.
A test case the skill fixed. Same model, same prompt, with and without the skill.
How do I detach a running subagent from my current subagent track interface so it continues independently?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that detaching is a user gesture in the subagents UI track without invoking API flags or create modes | Missed | Passed |
| Does not create a new workspace or agent handoff briefing | Passed | Passed |
The instructions your model reads when the skill loads.
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.
User's arguments: $ARGUMENTS
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.
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: "worktree", using a short branch name derived from the task.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
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.