Get the FREE Ultimate OpenClaw Setup Guide →

agent-coordination

npx machina-cli add skill a5c-ai/babysitter/agent-coordination --openclaw
Files (1)
SKILL.md
1.4 KB

Agent Coordination

Overview

Coordinate multi-agent work using Gas Town's role hierarchy: Mayor assigns, Crew persists, Polecats execute transiently, and hooks drive the GUPP principle ("If there is work on your Hook, YOU MUST RUN IT").

When to Use

  • Assigning beads to agents
  • Managing agent handoffs
  • Nudging stuck agents
  • Coordinating Crew and Polecat workers
  • Setting up hook hierarchies

Agent Types

  • Crew: Long-lived, named agents for persistent collaboration
  • Polecats: Transient workers with persistent identity but ephemeral sessions
  • Dogs: Deacon helpers for infrastructure tasks

Hook Hierarchy

Three-tier hook system (base -> role -> rig+role):

  1. Base hooks: Apply to all agents
  2. Role hooks: Apply to agents in a specific role
  3. Rig+Role hooks: Apply to agents on a specific rig in a specific role

Key Commands

  • gt agents - List available agents
  • gt feed - Feed work to an agent's hook
  • gt handoff - Hand off work between agents
  • gt nudge - Nudge a stuck agent
  • gt seance - Revive a dead agent session

Tool Use

Invoke via babysitter process: methodologies/gastown/gastown-orchestrator (assign-workers step)

Source

git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/gastown/skills/agent-coordination/SKILL.mdView on GitHub

Overview

Agent Coordination uses a three-tier hook hierarchy to manage Crew (persistent) and Polecat (transient) workers. It relies on Gas Town's hook-based work distribution and the GUPP principle to ensure work is executed when present on a hook. The Mayor assigns work and hooks drive targeted execution and handoffs.

How This Skill Works

Base hooks apply to all agents, role hooks apply to agents in a specific role, and rig+role hooks apply to agents on a specific rig within a role. The orchestrator exposes commands like gt agents, gt feed, gt handoff, gt nudge, and gt seance to distribute work, transfer tasks, recover stuck agents, and revive dead sessions.

When to Use It

  • Assigning beads to agents
  • Managing agent handoffs
  • Nudging stuck agents
  • Coordinating Crew and Polecat workers
  • Setting up hook hierarchies

Quick Start

  1. Step 1: List available agents with gt agents.
  2. Step 2: Feed work to a hook using gt feed.
  3. Step 3: Manage flow with gt handoff or gt nudge; revive if needed using gt seance.

Best Practices

  • Define clear roles (Mayor, Crew, Polecat, Dogs) and responsibilities to align expectations.
  • Leverage base/role/rig+role hooks to route tasks precisely to the right agents.
  • Prefer gt feed for distributing work and gt handoff for transitions between agents.
  • Use gt nudge to recover stuck agents and gt seance to revive dead sessions.
  • Document agent identities, rigs, and role mappings to inform future load distribution.

Example Use Cases

  • Assigning a workload to Crew via the appropriate base/role hooks using gt feed.
  • Coordinating a handoff from Crew to a Polecat for processing steps.
  • Nudging a stalled Polecat to resume work with gt nudge.
  • Reviving a dead session using gt seance to restore progress may be required.
  • Establishing a new three-tier hook hierarchy (base -> role -> rig+role) for a deployment.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers