hermes - 💡(How to fix) Fix [IMPROVEMENT] Skills in ~/.hermes/skills/ are unversioned hand-edited markdown [1 participants]

TL;DR

Implementing Git-backed skills by making ~/.hermes/skills/ a git repository and committing on every skill write is the most straightforward approach to address the issue of silently corrupted skills.

Guidance

• Consider the trade-offs between the proposed fix options, weighing the simplicity of Git-backed skills against the infrastructure leverage of Skill versioning in Mnemosyne.
• Evaluate the potential benefits of Signed skills for detecting corruption, but also consider the added complexity of implementing and managing HMAC tags.
• Assess the existing version control and backup processes for ~/.hermes/skills/ to determine if any partial solutions are already in place.
• Before implementing any solution, ensure that the chosen approach aligns with the overall system architecture and security requirements.

Example

No code snippet is provided due to the high-level nature of the issue and proposed solutions.

Notes

The choice of solution may depend on factors not mentioned in the issue, such as the specific requirements for skill management, the existing development workflow, and the security standards that must be met.

Recommendation

Apply the Git-backed skills workaround, as it is the simplest to implement and provides a straightforward version history and rollback path for skills.