paseo-advisor
Spin up a single agent as an advisor — second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an…
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.
$ npx -y skills add getpaseo/paseo --skill paseo-handoff --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/paseo-handoffContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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
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`.
1. **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. 2. **Isolation** — "in a worktree" / "worktree" → create a workspace with `isolation: "worktree"`, using a short branch name derived from the task. 3. **Task description** — anything else the user said.
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.
Prepare the handoff in a dedicated workspace:
1. Select the current workspace or call `create_workspace` with the requested isolation. 2. Call `create_agent` with a `[Handoff] <task>` title, the briefing as initial prompt, and the selected `workspaceId` when explicit placement is needed. 3. 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.
Repo: getpaseo/paseo
Spin up a single agent as an advisor — second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an…
Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a…
Answer questions about the Paseo product and app, including setup, configuration, connectivity, providers, workspaces, updates, logs, and troubleshooting. Use…
Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin;…
Paseo reference for managing projects, workspaces, workspace scripts, agents, schedules, and heartbeats.