paseo-handoff

The paseo-handoff skill transfers tasks to new agents by generating a structured briefing containing context, constraints, and progress. It integrates with the paseo skill to create agents and optional worktrees.

1.3K
Installs
3
Use cases
9/10
Quality

Is paseo-handoff safe to install?

Safe to install

Safe to install: our audit of paseo-handoff's source files found 0 shell commands, 0 external URLs, file reads and writes (low risk). Every command and URL listed appears verbatim in the skill's source. The skill reads local configuration files at ~/.paseo/orchestration-preferences.json to determine agent providers.

How we audit skills: our security review methodology.

Who is this skill for?

Users of the Paseo agent framework who need to delegate tasks to specialized agents while maintaining continuity of work.

What can you do with it?

  • Delegating complex tasks to a new agent with a clean context.
  • Creating a new worktree for a specific task branch.
  • Passing task history, failed attempts, and constraints to a successor agent.

How good is this skill?

Quality score: 9/10. The skill documentation is clear and provides a specific template for the handoff prompt. It correctly identifies the dependency on the paseo skill.

What does the skill file contain?

SKILL.md
# 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. Before choosing a provider, read `~/.paseo/orchestration-preferences.json` unless the user explicitly named a provider in this request. Do not create the receiving agent until you have read it.

## Parsing arguments

1. **Provider** — explicit user request first; otherwise resolve from `impl` prefer...

Frequently asked questions

How does the skill determine which agent provider to use?

It uses the provider specified by the user, or it reads the default provider from ~/.paseo/orchestration-preferences.json.

Does the receiving agent inherit the current agent's context?

No. The receiving agent starts with zero context, so the skill generates a self-contained briefing document.

Can the skill create a new worktree?

Yes. If the user specifies a worktree, the skill creates one via Paseo using a branch name derived from the task.

Data sourced from getpaseo/paseo on GitHub. Install counts from skills.sh. The summary and security audit are derived from the skill's source files: every command and URL listed appears verbatim in the source.