Review Agent-Generated Skill Changes Before Hermes Applies Them
Enable skill write approval to place agent-generated skill changes in a review queue. It is useful when an agent proposes to turn a one-off shortcut into reusable instructions that future sessions may load.
- Skill proposal
- Inspect staged diff
- Approve or reject
Stage a controlled change
Use a disposable profile and create a harmless fixture skill proposal, such as a procedure to print the .NET SDK version before a console build. Confirm your Hermes version supports the documented approval setting and review commands. Merge this key into the current profile configuration and start a fresh session:
skills:
write_approval: true
Ask the agent to propose the reusable procedure through its skill-management tool. Open /skills pending, identify the proposal, and use /skills diff ID with the displayed identifier. Review the actual text, any helper files, what tools they call, and which data they will read. A two-line change that adds a network command deserves closer review than an edit to a heading.
Verify both decisions
Reject the first proposal with the documented /skills reject ID command. Confirm that no resulting skill was applied. Ask for a corrected proposal scoped to the test project, review its diff, and approve only that identifier with /skills approve ID. Inspect the resulting skill and exercise it in another fresh session. The expected procedure reads the SDK version and runs the intended build inside the approved workspace.
For a team, require a reviewer to inspect changed helper files in addition to SKILL.md. Treat the text as future operational guidance and the helper as code. Store approved procedures with ordinary source review where possible and remove credentials from examples and test logs.
Limits of the gate
The documented gate applies to skill-management writes. Generic file tools or terminal access can modify files outside that path. Restrict those capabilities or the underlying workspace permissions when this must be an enforceable boundary. Test that the deployment handles both the approved path and the relevant bypass paths in a disposable profile.
Why is there nothing pending? Verify the profile and setting, and check whether the agent used the skill-management tool or another write path.
Should an edited proposal reuse its old approval? Review the current diff and identifier. An approval applies to the content reviewed.
References
Official Hermes Agent documentation · ASP.NET PB on MCP tools and resources
Comments
Post a Comment