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