[omh] Executor runtime readiness - compare Codex, Claude Code, Hermes coding, and oh-my runtimes by tools and handoff mode; use external-connector-readiness for a named plugin or API, and toolbelt-readiness for the whole capability inventory.
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 20 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill91%
Checks it passed that the model alone missed
Specifies using --output-format json.
Includes the flag --output-format json in the command call.
Formats the resume invocation as claude -p --resume <session-id>.
and 17 more in the full report
17 fixed3 passed either way2 still failing0 broke
Pass-rate lift
+77 pp
Tokens
+103%
Agent turns
0%
Response time
-42%
Model gemini-3.6-flashMeasured 8/19/2026v320 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
Which CLI argument enables JSON structured output parsing when initiating a non-interactive session in Claude Code?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies passing --output-format json in the execution invocation.
Missed
Passed
case-13 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md122 linessingle file
Executor Runtime Readiness
This is a Hermes-native executor-runtime-readiness workflow skill.
Why This Exists
executor-runtime-readiness exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
Do Not Use When
The request is already handled by a narrower explicit skill with stronger evidence.
The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
Examples
Good example:
Prompt: executor-runtime-readiness can this task run in Codex, Claude Code, or Hermes coding?
Expected behavior: Produce prepare_executor_runtime_readiness with required context, wrapper actions, and not-evidence boundaries.
Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
Prompt: executor-runtime-readiness claim Codex already started the session.
Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
The selected coding or runtime owner is named before any implementation claim.
Prepared handoff, dispatch, execution, verification, review, CI, and merge states are separated.
The final status cites observed runtime evidence or keeps the work prepared_not_observed.
When Hermes is the selected coding owner, use hermes_coding_harness/v1 to keep builder, verifier, reviewer, docs, and PR lanes separate.
Report the current harness stage, owner, next action, and missing evidence without claiming PR creation, review, CI, merge-readiness, or merge until matching runtime observations exist.
Recovery Notes
If the selected executor is unavailable, ask for Codex, Claude Code, Hermes, or another runtime before retrying.
If dispatch or result evidence is missing, keep the handoff prepared_not_observed and expose the next observable action.
[omh] Hermes Agent Evaluation workflow: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics. Use when the user says: agent-evaluation, agent evaluation, agent eval, agent benchmark, executor evaluation, executor benchmark, compare agents, compare codex claude.