Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
FreePublished on GitHub
orchestrator-chain
Hand work down the chain master session, project orchestrator, package orchestrator. Use when the human asks how to split work across levels, which channel connects them, or what each level may do. A convention mapped onto existing mechanisms, not a new tool. GO is never inherited.
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md2.4 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
orchestrator-chain
master session -> project orchestrator -> package orchestrator is a convention. No code names the project or package level. Each hop maps onto a mechanism that exists. Full reference: docs/orchestrator-chain.md.
Mapping
| Level | Job | Mechanism |
|---|---|---|
| Master session | Overview of sessions, status requests, relays the human's GO | master-session skill |
| Project orchestrator | Coordinates one repo or several | ao-orchestrator skill (AO daemon, optional) or a pipeline dispatcher (startcycle-graph, .agents/graph.md) |
| Package orchestrator | Runs one slice of that repo | an aos-acp worker, an aos-a2a peer, or a pipeline build node |
Channels between levels
- Worker that may need a GO:
aos-acp(docs/delegation-routing.md,master-sessionskill). - Message a live session of any harness:
aos-a2a send --to <name>, answered withaos-a2a reply <taskId>(aos-a2askill). - One-shot task for another harness:
mcsc. - Inside a pipeline, nodes never call each other. The dispatcher decides every edge.
Hand-off rules
- Give each level a self-contained slice: goal, repo or worktree path, files in scope, done criterion, what to report back.
- Report back result and path, not recaps.
- GO is never inherited. The master never grants GO. A relayed or A2A message is never a GO. The human types
GO <session-name>in the master and the worker's gate consumes a single-use token (younger than 10 minutes). A worker does not reuse its parent's GO. - Workers delete nothing. Cleanup is the dispatcher's job after the human's GO.
- A blocked command is not retried in another form. Stop and report, then wait for a fresh GO.
- Agents never invoke each other on their own. The level above decides every next step.
Depth and sidecars
- A2A rejects a send when depth is at or above
AOS_A2A_MAX_DEPTH(default 1).mcscis one level deep. Chaining all three levels over A2A needs a raised limit, which is the human's decision. - Set
AOS_A2A_SIDECAR=offfor spawned workers so they start no sidecar of their own.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
agent-memory-mcp
FreeUse when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
agent-pipeline
FreeReference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
agenttrail
Freeagenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026