| name | execution-router |
| description | Classify tasks by complexity and route heavy isolated coding work to Codex CLI with the correct current command syntax. |
| version | 1.0.0 |
| author | Chris Cortex |
| license | MIT |
| platforms | ["macos","linux"] |
| metadata | {"hermes":{"tags":["routing","codex","delegation","orchestration"],"related_skills":["codex","plan","mac-cortex"],"requires_tools":["terminal"]}} |
Execution Router
Use this skill when a task should be delegated or broken into a smaller execution slice.
Classification
- Simple: answer directly or run one small command yourself.
- Medium: inspect, plan briefly, execute in Hermes, then verify.
- Heavy isolated coding: route to Codex CLI with a concrete implementation prompt.
Codex Routing
Use the wrapper script:
~/.hermes/skills/execution-router/scripts/delegate_to_codex.sh "your concrete implementation prompt" "/absolute/workdir"
Default mode is --full-auto, which keeps Codex inside its workspace-write sandbox.
If the user explicitly wants the most permissive path and the environment is already trusted, add --dangerous:
~/.hermes/skills/execution-router/scripts/delegate_to_codex.sh --dangerous "prompt" "/absolute/workdir"
Rules
- Route only bounded coding tasks, not vague life-management requests.
- Use the real installed syntax:
codex exec, not deprecated or invented flags.
- Prefer the current repository as the workdir.
- If the workdir is not a git repo, the wrapper will create a temporary scratch repo.
- Always pass a concrete prompt with scope, files, and verification expectations.
Verification
- Confirm Codex exited successfully.
- Read the wrapper summary and inspect resulting diffs or files before reporting completion.
