Hermes Acp Orchestrator
Delegate subtasks from Hermes to hermes, Codex, or Claude Code with ACP-style routing, output caps, and timeouts so multi-agent runs stay bounded.
Overview
hermes-acp-orchestrator is an agent skill most often used in Build (also Ship testing, Operate iterate) that routes Hermes delegation to hermes, codex, or claude-code with output limits and timeouts.
Install
npx skills add https://github.com/Rainhoole/hermes-agent-acp-skill --skill SKILL.mdWhat is this skill?
- ACP-style delegation with explicit routing targets: hermes, codex, and claude-code
- Safe output limits to prevent runaway delegated responses
- Timeout-aware execution for long-running sub-agent tasks
- Designed for Hermes-hosted workflows that fan out work instead of one monolithic chat
- Composable with other repo skills once routing rules are defined
- Explicit routing to 3 delegate targets: hermes, codex, and claude-code
Adoption & trust: 38 GitHub stars.
What problem does it solve?
You need multiple coding agents in one workflow but get chaotic handoffs, unbounded logs, or hung delegate calls.
Who is it for?
Builders already on Hermes who want repeatable ACP-style routing to Codex or Claude Code for parallel implementation or review slices.
Skip if: Single-agent-only workflows with no Hermes runtime, or teams that only need a static prompt without delegation semantics.
When should I use this skill?
Use when you need ACP-style delegation in Hermes with explicit agent routing to hermes, codex, or claude-code, including safe output limits and timeout-aware execution.
What do I get? / Deliverables
Hermes runs issue bounded sub-agent jobs with explicit targets and timeout-aware completion instead of one overloaded conversation.
- Bounded delegate responses merged back into the parent Hermes session
- Documented routing choice per subtask (hermes, codex, or claude-code)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build → agent-tooling is the primary shelf because the skill is about orchestrating coding agents during implementation, not about distribution or ops monitoring. Agent-tooling subphase captures explicit routing between Hermes and downstream coding agents—the core value of the orchestrator.
Where it fits
Route a backend migration slice to Codex while Hermes keeps repo context and merges summaries.
Delegate an unfamiliar SDK spike to Claude Code with a strict response size cap.
Fan out flaky test investigation to a delegate agent with a hard timeout.
Re-run a bounded fix pass through the same router after production feedback.
How it compares
Orchestration skill for routed multi-agent execution, not a standalone MCP server or a generic planning template.
Common Questions / FAQ
Who is hermes-acp-orchestrator for?
Solo and small-team builders using Hermes who delegate coding work to Codex or Claude Code and need explicit routing and safety limits.
When should I use hermes-acp-orchestrator?
Use it while building agent-tooling in Build, when splitting Ship testing or review across agents, and during Operate iterate cycles that re-run scoped fixes through the same router.
Is hermes-acp-orchestrator safe to install?
Delegation skills can trigger shell and network actions via child agents; review the Security Audits panel on this Prism page and tighten timeouts and output caps in your environment.
SKILL.md
READMESKILL.md - Hermes Acp Orchestrator
Use when you need ACP-style delegation in Hermes with explicit agent routing to hermes, codex, or claude-code, including safe output limits and timeout-aware execution. # hermes-acp-orchestrator { "name": "hermes-acp-orchestrator", "description": "Use when you need ACP-style delegation in Hermes with explicit agent routing to hermes, codex, or claude-code, including safe output limits and timeout-aware execution." }