Severity: Medium
Problem: Skills stored in ~/.hermes/skills/ are hand-edited markdown files with no version history, no diff capability, and no rollback path. A bad skill patch silently corrupts future agent behavior — the agent just loads the wrong skill without warning. This is especially risky because skills encode exact tool commands, pitfalls, workflow conventions, and user preferences.
Proposed fix options:
- Git-backed skills — make
~/.hermes/skills/ a git repo and commit on every skill write
- Skill versioning in Mnemosyne — store skill versions as memories with timestamps, allow rollback via
skill_manage
- Signed skills — HMAC-tag skill content to detect silent corruption
Option 1 is simplest to implement; Option 2 leverages existing Mnemosyne infrastructure.
Severity: Medium
Problem: Skills stored in
~/.hermes/skills/are hand-edited markdown files with no version history, no diff capability, and no rollback path. A bad skill patch silently corrupts future agent behavior — the agent just loads the wrong skill without warning. This is especially risky because skills encode exact tool commands, pitfalls, workflow conventions, and user preferences.Proposed fix options:
~/.hermes/skills/a git repo and commit on every skill writeskill_manageOption 1 is simplest to implement; Option 2 leverages existing Mnemosyne infrastructure.