Doctor
This is a Hermes-native doctor workflow skill.
Why This Exists
doctor exists to turn confusing install/setup states into grouped, local health evidence and the next repair action without treating a check as a fix.
Do Not Use When
- The user is asking for a general product explanation rather than local health diagnostics.
- The requested change is a repository bug fix, not an installed-environment check.
- The wrapper wants to claim Hermes reload, skill execution, or plugin behavior that was not observed.
Examples
Good example:
- Prompt: doctor after omh update says setup is next but Hermes skills still look stale.
- Expected behavior: Inspect managed skills, Hermes registration, runtime state, and next repair action with explicit proof boundaries.
- Why: The issue is local installation health and needs grouped diagnostic evidence.
Bad example:
- Prompt: doctor implement a new uninstall command UX.
- Expected behavior: Route to planning or implementation instead of health diagnostics.
- Why: That is product development work, not a local health check.
Completion Checklist
- Command availability, managed skills, Hermes registration, runtime state, and optional surfaces are grouped separately.
- Blocking issues and warnings are separated, with one next repair action named for each blocking area.
- Plugin install, plugin import/register smoke, and Hermes runtime load are not collapsed into one claim.
- The final status says whether setup/update/doctor repaired anything or only observed health.
Recovery Notes
- If managed skills are stale, recommend omh update or omh setup depending on whether registration also needs repair.
- If skills.external_dirs or Hermes config is missing, route to setup repair rather than editing hidden runtime state.
- If plugin register smoke fails, reinstall the plugin bundle with setup --with-plugin --force before claiming plugin readiness.
- If omh is missing from PATH, use the installer-reported absolute command path and then re-run doctor.
Workflow Lane
- Current lane: Automation and status (
achievements, workspace-audit, production-audit, automation-blueprint, github-event-ops, github-issue-intake, buzz, agent-board, +35 more) - schedules, status, health, and ops review.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use to diagnose OMH installation and Hermes config registration.
Strong routing signals: `doctor`, `$doctor`, `diagnose omh`, `installation health`
Catalog Metadata
Category: operator
Phase: diagnostics
Hermes role: tracker
Quality tier: evidence-gated
Reasoning demand: light
Quality bar:
- Name the workflow target, constraints, validation evidence, and stop condition.
- Separate Hermes guidance from executor or wrapper behavior unless evidence proves the step happened.
Handoff policy:
Run directly as local health inspection; propose executor work only when a repo fix is required.
Required inputs:
- omh home
- Hermes home
- observed issue
Expected outputs:
- health checks
- fix guidance
- known proof boundary
Artifact expectations:
- doctor state summary when runtime artifacts are writable
Safety rules:
- Do not imply hidden Hermes runtime behavior.
- Use the smallest verification that can prove the claim.
Runtime Evidence
Preferred harness for this skill: qa-specialist.
omh runtime record --skill doctor --harness qa-specialist --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---
2name: "omh-doctor"
3description: "[omh] Hermes adaptation for diagnosing oh-my-hermes installation health. Use when the user says: doctor, diagnose omh, installation health."
4metadata:
5 hermes:
6 tags: [workflow, oh-my-hermes, operator]
7 category: operator
8 phase: diagnostics
9 role: tracker
10 quality_tier: evidence-gated
11---
12
13# Doctor
14
15This is a Hermes-native `doctor` workflow skill.
16
17## Why This Exists
18
19`doctor` exists to turn confusing install/setup states into grouped, local health evidence and the next repair action without treating a check as a fix.
20
21## Do Not Use When
22
23- The user is asking for a general product explanation rather than local health diagnostics.
24- The requested change is a repository bug fix, not an installed-environment check.
25- The wrapper wants to claim Hermes reload, skill execution, or plugin behavior that was not observed.
26
27## Examples
28
29Good example:
30
31- Prompt: doctor after omh update says setup is next but Hermes skills still look stale.
32- Expected behavior: Inspect managed skills, Hermes registration, runtime state, and next repair action with explicit proof boundaries.
33- Why: The issue is local installation health and needs grouped diagnostic evidence.
34
35Bad example:
36
37- Prompt: doctor implement a new uninstall command UX.
38- Expected behavior: Route to planning or implementation instead of health diagnostics.
39- Why: That is product development work, not a local health check.
40
41## Completion Checklist
42
43- Command availability, managed skills, Hermes registration, runtime state, and optional surfaces are grouped separately.
44- Blocking issues and warnings are separated, with one next repair action named for each blocking area.
45- Plugin install, plugin import/register smoke, and Hermes runtime load are not collapsed into one claim.
46- The final status says whether setup/update/doctor repaired anything or only observed health.
47
48## Recovery Notes
49
50- If managed skills are stale, recommend omh update or omh setup depending on whether registration also needs repair.
51- If skills.external_dirs or Hermes config is missing, route to setup repair rather than editing hidden runtime state.
52- If plugin register smoke fails, reinstall the plugin bundle with setup --with-plugin --force before claiming plugin readiness.
53- If omh is missing from PATH, use the installer-reported absolute command path and then re-run doctor.
54
55## Workflow Lane
56
57- Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `github-issue-intake`, `buzz`, `agent-board`, `+35 more`) - schedules, status, health, and ops review.
58- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
59- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
60
61## Use When
62
63Use to diagnose OMH installation and Hermes config registration.
64
65 Strong routing signals: `doctor`, `$doctor`, `diagnose omh`, `installation health`
66
67## Catalog Metadata
68
69Category: `operator`
70Phase: `diagnostics`
71Hermes role: `tracker`
72Quality tier: `evidence-gated`
73Reasoning demand: `light`
74
75Quality bar:
76
77- Name the workflow target, constraints, validation evidence, and stop condition.
78- Separate Hermes guidance from executor or wrapper behavior unless evidence proves the step happened.
79
80Handoff policy:
81
82Run directly as local health inspection; propose executor work only when a repo fix is required.
83
84Required inputs:
85
86- omh home
87- Hermes home
88- observed issue
89
90Expected outputs:
91
92- health checks
93- fix guidance
94- known proof boundary
95
96Artifact expectations:
97
98- doctor state summary when runtime artifacts are writable
99
100Safety rules:
101
102- Do not imply hidden Hermes runtime behavior.
103- Use the smallest verification that can prove the claim.
104
105## Runtime Evidence
106
107Preferred harness for this skill: `qa-specialist`.
108
109```sh
110omh runtime record --skill doctor --harness qa-specialist --status started
111```
112
113Record observed delegation results; otherwise return `not_available` or `not_observed`.
114Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
115- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
116Preserve workflow intent and stop conditions; verify before claiming completion.
117
118Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
119
120Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.
rlaope