Skip to content
Back to skills

Handoff Orchestrator

ASecurity

Use when an approved work scope moves to a new orchestrator in its own Herdr tab.

  • 4 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsgo

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add wayne930242/straw-boss --skill handoff-orchestrator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Handoff Orchestrator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Handoff Orchestrator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wayne930242-handoff-orchestrator/badge)](https://www.skillsdirectory.com/skills/wayne930242-handoff-orchestrator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: handoff-orchestrator
description: Use when an approved work scope moves to a new orchestrator in its own Herdr tab.
---

# Hand off one orchestrator scope

## 1. Get approval

A handoff creates another user-facing window, so the current main agent first presents one approval decision, naming the scope that moves and any work this orchestrator retains.
A new tab is created only after the user approves.

## 2. Carry continuity

Pass only goal and scope, confirmed decisions and user terms, current state and evidence, next action, and exclusions.
Omit empty fields and conversation text.

## 3. Launch and transfer

Run `handoff-orchestrator.py` with `--user-approved`, this pane, cwd, provider, and the continuity fields.
Pass `--dispatch` for each in-progress dispatch in the moving scope; a handoff that retains nothing lists every dispatch this pane coordinates.
The script creates and labels an independent tab, starts the receiving orchestrator, prompts it to invoke `boss-say` and then accept, and verifies the handshake after that route is established.
It waits up to two 120-second acceptance windows, re-offering only to a receiver that stopped without accepting, so give the command a tool timeout of at least five minutes.
Final failure closes the new tab and leaves ownership here.

## 4. Leave the scope

On acceptance, status events, investigation, scheduling, reporting, and cleanup all belong to the receiver.
Report the new tab and transferred scope compactly.
Continue only the scope passed through `--retains`.
When none is retained, let the launcher close this pane after it emits the accepted result.

**Complete when:** the receiver accepted and this orchestrator left the scope, or the failed new tab is closed and ownership remains here.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.