SKILLS RELIABILITY
Hermes Skills Fail to Load Despite Valid Configuration #66383
A documented P3, needs-reproduction issue where intended skills remain unavailable even when the configurator and expected folder structure appear valid.
Documented behavior
The report describes skills that remain unavailable despite an apparently correct configurator setup and expected directory layout. Until a minimal reproduction establishes the cause, operators should treat the path and UI confirmation as necessary but insufficient evidence that a skill is active.
Evidence boundary: This page summarizes a reported issue and a cautious reproduction protocol. It does not establish that every configuration or installation is affected.
Verification matrix
| Check | What to inspect | Bounded response |
|---|---|---|
| Directory discovery | Does the running process resolve the exact expected skills directory? | Confirm the effective runtime path and ownership, not only the folder visible in a file browser. |
| Configurator state | Does the saved configurator entry survive reload and point to the intended location? | Reopen the configuration and compare the persisted value with the runtime path. |
| Load evidence | Is there an explicit loading record, warning, or error for the intended skill? | Collect the smallest relevant startup or diagnostic evidence, with sensitive values removed. |
| Minimal reproduction | Can one simple skill fail in an otherwise clean setup? | Reduce to one skill and one directory before testing broader integrations. |
Reproduction and recovery protocol
- Create a minimal non-sensitive skill fixture with an unmistakable name and expected behavior.
- Confirm the configured directory path, process user, and read permissions.
- Restart the relevant runtime and capture loading diagnostics or the absence of the fixture.
- Test the same fixture in a clean, documented environment to separate setup effects from a product defect.
- Share a minimal reproduction with exact versions, paths, and redacted diagnostics if the skill still does not appear.
Source evidence
GitHub issue #66383 · P3 · Needs reproduction · Opened July 17, 2026
Issue status and scope can change. Review the linked record before relying on this page for a production decision.