What problem does it solve? When a Hames installation misbehaves, users cannot tell whether the cause is broken configuration, missing files, stale locks, or hooks that the host never executed. This Skill inspects the installation without changing anything and reports actionable recovery options. ## Core Features & Use Cases - Read-only diagnosis: Checks config parsing and schema, required .hames/ paths, entry boundary blocks, contract hashes, progress, review and knowledge linkage, evidence linkage, session ownership, the four bundled skills, and hook files. - Separated evidence: Distinguishes configured state, observed runtime behavior, and checks that have not been run, so a file's presence is never mistaken for host discovery or hook execution. - Safe recovery guidance: Shows each failed check's impact and only recovery actions the bundled runtime supports, requiring an explicit choice before changing a lock. - Use Case: After installing the Hames plugin, your indexes stop updating. Invoke /doctor to run the bundled runtime/doctor.js, see which checks failed, and get a supported recovery path without any files being modified. ## Quick Start Ask the agent to run /doctor against the current project root and report which configuration and hook checks failed.