doctor
starsforks
How to install doctor?
rlaope/oh-my-hermes/doctor
$npx -y skills add rlaope/oh-my-hermes --skill doctor[omh] Hermes adaptation for diagnosing oh-my-hermes installation health.
SKILL.md
| 1 | # Doctor |
| 2 | |
| 3 | This is a Hermes-native `doctor` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `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. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user is asking for a general product explanation rather than local health diagnostics. |
| 12 | - The requested change is a repository bug fix, not an installed-environment check. |
| 13 | - The wrapper wants to claim Hermes reload, skill execution, or plugin behavior that was not observed. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: doctor after omh update says setup is next but Hermes skills still look stale. |
| 20 | - Expected behavior: Inspect managed skills, Hermes registration, runtime state, and next repair action with explicit proof boundaries. |
| 21 | - Why: The issue is local installation health and needs grouped diagnostic evidence. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: doctor implement a new uninstall command UX. |
| 26 | - Expected behavior: Route to planning or implementation instead of health diagnostics. |
| 27 | - Why: That is product development work, not a local health check. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Command availability, managed skills, Hermes registration, runtime state, and optional surfaces are grouped separately. |
| 32 | - Blocking issues and warnings are separated, with one next repair action named for each blocking area. |
| 33 | - Plugin install, plugin import/register smoke, and Hermes runtime load are not collapsed into one claim. |
| 34 | - The final status says whether setup/update/doctor repaired anything or only observed health. |
| 35 | |
| 36 | ## Recovery Notes |
| 37 | |
| 38 | - If managed skills are stale, recommend omh update or omh setup depending on whether registration also needs repair. |
| 39 | - If skills.external_dirs or Hermes config is missing, route to setup repair rather than editing hidden runtime state. |
| 40 | - If plugin register smoke fails, reinstall the plugin bundle with setup --with-plugin --force before claiming plugin readiness. |
| 41 | - If omh is missing from PATH, use the installer-reported absolute command path and then re-run doctor. |
| 42 | |
| 43 | ## OMH Context Rail |
| 44 | |
| 45 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 46 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 47 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 48 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 49 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 50 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 51 | - Coverage: Every generated workflow skill carries this rail. |
| 52 | - Normal users talk to Hermes; OMH CLI is infra. |
| 53 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 54 | |
| 55 | ## Use When |
| 56 | |
| 57 | Use to diagnose OMH installation and Hermes config registration. |
| 58 | |
| 59 | Strong routing signals: `doctor`, `$doctor`, `diagnose omh`, `installation health` |
| 60 | |
| 61 | ## Catalog Metadata |
| 62 | |
| 63 | Category: `operator` |
| 64 | Phase: `diagnostics` |
| 65 | Hermes role: `tracker` |
| 66 | Quality tier: `evidence-gated` |
| 67 | |
| 68 | Quality 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 | |
| 73 | Handoff policy: |
| 74 | |
| 75 | Run directly as local health inspection; propose executor work only when a repo fix is required. |
| 76 | |
| 77 | Required inputs: |
| 78 | |
| 79 | - omh home |
| 80 | - Hermes home |
| 81 | - observed issue |
| 82 | |
| 83 | Expected outputs: |
| 84 | |
| 85 | - health checks |
| 86 | - fix guidance |
| 87 | - known proof boundary |
| 88 | |
| 89 | Artifact expectations: |
| 90 | |
| 91 | - doctor state summary when runtime artifacts are writable |
| 92 | |
| 93 | Safety rules: |
| 94 | |
| 95 | - Do not imply hidden Hermes runtime behavior. |
| 96 | - Use the smallest verification that can prove the claim. |
| 97 | |
| 98 | ## Harness Discipline |
| 99 | |
| 100 | - Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes. |
| 101 | - Prefer richer evidence and clearer stop conditions over adding more workflow names. |
| 102 | - Use specialist lanes only when they change the quality of the |
People who liked this also viewed
6 picksType
- azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026
- safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026
- explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026
- minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026
- insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 2026
