Which Hermes skill revision passes your release tests?
Use a source-qualified Hermes target, then promote a revision only after a clean Docker trial reproduces every required result and confirms which skill files loaded.
Record the skill Hermes actually loads
Hermes documents a primary skills directory plus optional external directories. A source-qualified target identifies what you requested at install time. For release approval, record what the agent actually read during a trial. Start with the installed instructions, follow any referenced scripts or resources, and record a digest for the reviewed bundle. In a disposable profile, put the same short name in two configured roots and give each copy a distinct benign marker, such as returning a different label for one synthetic record. Inspect the loaded path if your setup exposes it, and verify the marker in the result. An unexpected marker or an ambiguous result is grounds to remove the duplicate from the trial configuration and repeat the test before promotion.
Skills System | Hermes AgentHold the runtime still while you change the skill
The Hermes Docker guide describes a stateless image and a host-backed data directory at /opt/data. Use the same image digest for baseline and candidate runs, with separate disposable data roots for each. Record the model and fixture inputs, then compare observable outputs case by case. For a skill that turns invoices into a table, include a synthetic invoice with a missing tax amount and one with two differently formatted line items. Require exact output for a normalized record or an explicit missing-field result. Also include a prompt that should yield an ordinary response without invoking the skill, and count any unwanted invocation as a failed case. Replacing the image while reusing the same data can leave the installed skill intact, so record the skill bundle digest separately from the runtime image digest.
Hermes Docker Setup | Hermes AgentPick the source before opening an install link
Hermes copies bundled skills from its repository during a fresh install. For an additional skill, start with the official optional catalog and compare the relevant entry with any community result. Hermes Desktop supports source-qualified install links, including official optional and ClawHub targets. Use that distinction to identify the publisher and source before opening the link. Consult the live catalog for current availability because catalog size says little about whether a particular skill fits your task.
Read the skill instructions and any scripts before choosing a candidate. List the files, services, and permissions it expects and check them against the work it needs to do. Hold the install if you cannot identify the source or explain a requested permission.
Skills System | Hermes AgentUse one fixture before granting real access
In an illustrative trial, you need a skill to turn an exported issue list into a release summary. Give the test Hermes instance six synthetic issues, four marked for release and two marked internal. Require a local draft containing exactly the four approved IDs. Compare the bundled or official optional candidate with a community candidate using the same input, and note which files and tools each needs.
Hermes documents a Docker deployment that puts user data, including skills and API keys, in a host directory mounted at /opt/data. Give the trial its own data directory and keep production credentials and mounts outside it. A candidate passes when the draft matches the expected IDs and observed actions stay within the allowed files and tools. Unexpected writes or network requests stop the trial.
Hermes Docker Setup | Hermes AgentCheck the active skill directory first
Hermes documents symlink support for its home directory and subdirectories including skills. If startup fails after moving the skill storage, read the storage error before reinstalling anything. Check the named path and link target, confirm the target exists and is a directory, and confirm the account running Hermes can access it. Then restart and look for the selected skill from the same instance you intend to use.
If Hermes starts but the task still behaves unexpectedly, check that you are testing the intended instance and inspect its skill directory plus any external skill directories configured for that instance. Compare the installed instructions with the reviewed copy, then rerun the six-issue fixture. File presence shows that the files are accessible. The fixture checks whether the agent actually follows the expected procedure.
Install Hermes Agent: Official Guide | Nous ResearchTreat updates as new installation decisions
Hermes loads skills on demand and can modify or delete them. Keep a reviewed copy or a source revision for any skill that matters to a recurring workflow. Before adopting an update, compare instructions, scripts, and dependencies with that baseline. If the update asks for a broader write path or a new integration, test that requirement in the trial instance before granting it to the working agent.
For the release-summary example, suppose an updated skill adds an optional publishing step. Keep the fixture's acceptance check at a local draft if that is the task you approved. If you need publishing, test it separately with a restricted credential and a disposable destination. If either test fails, restore the reviewed copy and rerun the fixture to confirm recovery.
Skills System | Hermes Agent