How do I install the Paseo Handoff skill?

Run npx skillmds@latest add gabrielmoreira/paseo-handoff in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Paseo Handoff safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Paseo Handoff?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Paseo Handoff free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Paseo Handoff?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Paseo Handoff by gabrielmoreira — Agent Skill

Name: Paseo Handoff
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

File contents

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.

User's arguments: $ARGUMENTS

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.

---name: paseo-handoffdescription: 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.---# Handoff SkillTransfer 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## PrerequisitesRead 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 arguments1. **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 handoff promptThe 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.## LaunchPrepare 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.

Frequently asked questions

Paseo Handoff