| name | ao-operator-discipline |
| description | Use when spawning, steering, or auditing Agent Orchestrator workers, especially when the user specifies exact AO parameters such as codex, runtime, project, claim-pr, or PR targets. |
AO Operator Discipline
Overview
AO parameters are commitments. If the user asks for Codex workers, PR-specific workers, a certain runtime, or a specific project, you must pass those parameters explicitly and then verify that AO actually honored them.
The failure pattern this skill prevents is simple: a worker exists, but it is the wrong worker.
When to Use
Use this skill when:
- the user asks to use AO or
ao
- you plan to run
ao spawn, ao send, ao session claim-pr, or ao status
- the user specifies a worker type such as Codex, Claude, Gemini, or a runtime
- you are claiming PRs or creating a PR-focused worker fleet
Do not use this skill for tiny read-only checks like a one-off ao status.
Agent Name Resolution — Read Config First
Before evaluating any --agent value, read the active AO config:
head -20 ~/.hermes/agent-orchestrator.yaml
--agent values are resolved against the config, not against AO package plugin directories. If <X> in --agent <X> is not a well-known CLI name (codex, claude, claude-code, gemini), look it up in the config before concluding it's unsupported.
Known shorthands on this machine:
agy / antigravity → (Google Antigravity / Gemini CLI) —
