rlaope/oh-my-hermes / skills/omh-routing
omh-routing
Verified[omh] Choosing among OMH skills for a request: router guidance for using oh-my-hermes workflow skills inside Hermes Agent.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.4 KB |
| references/catalog-index.md | markdown | 32.9 KB |
| references/coding-handoff-progress-reporting.md | markdown | 4.8 KB |
| references/evidence-boundaries.md | markdown | 2.6 KB |
| references/harness-registry.md | markdown | 21.4 KB |
| references/human-voice.md | markdown | 7.1 KB |
| references/jev-rail.md | markdown | 6.3 KB |
| references/operator-maintenance.md | markdown | 2.1 KB |
| references/skill-common-rail.md | markdown | 15.5 KB |
| references/structural-code-search.md | markdown | 3.8 KB |
| references/workflow-artifacts.md | markdown | 2.6 KB |
| references/workflow-registry.md | markdown | 33.4 KB |
| references/wrapper-routing.md | markdown | 11.3 KB |
references/operator-maintenance.md
View on GitHub# OMH Operator Maintenance
Short OMH maintenance commands are operator commands, not workflow or coding requests.
## Top Priority Guard
Exact or near-exact requests such as `omh update`, `omh setup`, `omh doctor`, `omh uninstall`, `omh install`, `omh list`, `omh 업데이트해줘`, `omh 닥터 돌려줘`, `omh 삭제해줘`, and `omh 셋업해줘` route as `operator_maintenance_command` with task type `omh_cli_maintenance`.
They outrank stale coding context, router-design feedback, runtime portability, migration, and workflow implementation signals unless the user explicitly asks for code changes.
`omh uninstall` with no flag removes all OMH-managed local state, the plugin bundle, the installer-managed `omh` command, and the Hermes config keys OMH set, with no confirmation prompt. Run `omh uninstall --dry-run` first, show what it would remove, and run the real command only after the user confirms (add `--keep-command` to keep the `omh` command). `--registration-only` removes only the `skills.external_dirs` registration.
## Semantics
- `route_level`: `operator_maintenance_command`
- `not_a_workflow`: `coding_handoff`, `router_design_feedback`, `runtime_portability`, `migration`, `workflow_implementation`
- `operation_primitives`: `run_requested_command`, `optional_health_check`, `report_observed_output`, `avoid_repo_mutation`
- `risk_domains`: `stale_context_inheritance`, `over_execution`, `unrequested_repo_mutation`
## Wrapper Copy
Say: "I will run the OMH maintenance update path; code changes require a separate request." Adapt `update` to the requested command; for `uninstall` say "I will preview the OMH uninstall with `--dry-run` first".
## Evidence Boundary
The requested command output and optional doctor status can become observed evidence. Future Hermes reload, plugin runtime use, coding work, review, CI, and repository mutation stay unobserved unless separately verified.
## Human Summary Vs JSON
Maintenance commands should prefer compact human summaries for chat/operator flows. Full `--json` output remains available for wrappers, automation, and tests that need machine-readable state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |