omh-routing
Oh My Hermes Router
Reasoning demand: light
Use this skill when the user mentions oh-my-hermes or a workflow keyword such as deep-interview, ultraperf, ralplan, loop, product-docs, research, research-department, source-finder, paper-learning, long-document-reading, data-analysis, command-operator, connector-operator, live-info-operator, external-connector-readiness, physical-device-readiness, content-operator, media-input-operator, feedback-triage, finance-analysis, people-ops, legal-compliance-review, support-operations, curriculum-design, localization-review, sales-development, product-brief, materials-package, img-summary, design-quality-gate, frontend, accessibility-audit, visual-qa, browser-operator, workspace-file-operator, automation-blueprint, harness-session-inventory, agent-debug, failure-signal-audit, instinct-ledger, skill-scout, skill-health, workflow-learning, codebase-onboarding, codegraph-refresh, codebase-uml, context-budget-review, run-efficiency, provider-profile-posture, decision-recall, security-safety-review, application-threat-model, live-incident-response, code-review, build-failure-triage, ultrawork, ultraqa, doctor.
Routing Contract
This is best-effort Hermes prompt guidance. It does not override Hermes core routing and it does not claim exact runtime parity with another agent framework.
Normal users should talk to Hermes Agent or invoke installed Hermes skills. Do not ask chat users to run omh; it is bootstrap and backend infrastructure.
Why This Exists
oh-my-hermes exists to keep Hermes chat routing conservative: it maps plain requests to the right workflow, explains evidence boundaries, and avoids making every keyword look like hidden implementation.