hermes bundles delete yml-only exited 1. The error named yml-only.yaml. That file was not in the bundles directory. hermes bundles show yml-only exited 0 on the next command and printed late-name.yml. The list still had one row, /yml-only, and the .yml file was still on disk.
That is the file identity Hermes Agent v0.22.5 used on 17 November 2026. hermes --version reported v0.22.5+471.g5894e75, commit 5894e750c3db, Python 3.14.9, on Linux x86_64. Each command ran with HERMES_HOME pointed at a new directory, not the operator home. The operator home had no skill-bundles directory before the run and none after. No model call was made. No gateway was started. The slash-path check used hermes --run-module on that same checkout, so the builder and the CLI were the same process family. v0.23.2 was tagged on 16 November 2026. This host did not run it. The skills page fetched the same night still tells you bundles live at ~/.hermes/skill-bundles/<slug>.yaml and that delete removes that bundle.
The File line is the loaded bundle
A bundle is a small YAML file. The name field is what the slash command uses, after a slug step. Backend Dev, backend_dev, and backend-dev all resolved to /backend-dev and all printed the same file, backend-dev.yaml. Spaces and underscores became hyphens. The filename the create command wrote was the slug plus .yaml.
Show is not looking up that filename. It looks up the slug, then prints whichever file the scan kept for that slug. The path is the File: line. List does not print a path. It prints the command, the name, a skill count, and the description. If you delete from the list row, you are deleting a name. You are not deleting the path show would have printed.
The skills page says the file is the slug with a .yaml suffix. Create follows that sentence. Show follows the scan. Those are different lookups. Delete follows the create path, not the show path.
Delete always names slug.yaml
The only file in one home was late-name.yml. Its name field was yml-only, the description was yml only, and the skill list held one entry, yml-skill. List printed /yml-only and a skill count of 1. Show printed the .yml path and exited 0. Delete did not remove it.
No bundle at $HERMES_HOME/skill-bundles/yml-only.yaml
The exit code was 1. A second show printed the same .yml path and exited 0. The file was still there. A wrapper that treats a failed delete as “already gone” will leave /yml-only in place. The failure means the canonical path was absent. It does not mean the command was absent.
A .yml file is a real bundle on this binary. It is not a draft the scanner ignores. It is also not a file delete knows how to name. The command you type is the slug. The path delete builds is always that slug with a .yaml suffix. The extension show printed is not an input to that path. If you copied a bundle from a tool that writes .yml, or you renamed the file and left the name field alone, show will load it and delete will refuse it. The refusal is consistent. It is not a check that the slash command is gone.
A zero exit can remove the unused file
The other failure looks like success. Three files shared the slug desk-route.
a-pack.yaml
desk-route.yaml
desk-route.yml
a-pack.yaml set the name to desk-route, the description to alphabetically first file, and one skill, first-file-skill. desk-route.yaml was the file create had written earlier, with invoice-desk and crash-desk. desk-route.yml set the same name and a different skill, yml-skill.
List showed one /desk-route row, not three. The description was alphabetically first file. Show printed a-pack.yaml. The other two files were on disk and were not the command.
hermes bundles delete desk-route exited 0 and printed a deleted-bundle line for desk-route.yaml. That is the path create writes. It is not the path show had just printed. After the delete, desk-route.yaml was gone. a-pack.yaml and desk-route.yml remained. List still had /desk-route. Show still printed a-pack.yaml and still exited 0.
A second delete exited 1 and named desk-route.yaml again. The command was still loaded. The success line from the first delete is the dangerous one. It names a real file, the exit code is 0, and the slash command you asked to remove is the file it did not touch. If a script deletes and then continues because the exit code was 0, it has removed an unused file and left the file show still prints. The command remains /desk-route. The skill list remains the one from a-pack.yaml. This pairing was not passed through the slash builder. Show is what proved the command was still bound to that file.
A later pairing showed the same winner rule across extensions. m-pack.yaml and late-name.yml both set the name to yml-only. Show printed m-pack.yaml and the description from that file, later yaml stem. The .yml name sorts first if you sort the directory as one list of filenames. The scan did not do that. The yaml file won. This run did not try uppercase names, unicode stems, or a directory symlink. For these lowercase names, the loaded file was the yaml, and within yaml it was the earlier filename, not the file whose stem matched the slug.
That order matters if you keep a hand-written pack beside the file create owns. A filename that sorts first, with the same name field, hides the canonical file from show. Delete still aims at the canonical file. You can remove the file you think is the bundle and leave the file show still prints. Read the File line. The filename in the directory listing is not enough, because more than one file can carry the same name field.
Create can describe a different bundle
--force does not change which file the slug uses. With a-pack.yaml still winning, create was asked to write desk-route again, with one skill flag, replaced-skill, the description forced rewrite, and force set. The exit code was 0. The created-bundle line named desk-route.yaml. The next line said /desk-route loads 2 skills.
The file it had just written contained one skill, replaced-skill, and the description forced rewrite. Show, run immediately after, printed a-pack.yaml, description still first, and two skills, first-file-skill and second-file-skill. The 2 in the create line was the winner’s list. It was not a count of the file the create line named, and it was not a count of skills that resolve on disk.
The first create of the night had the same wording with no collision. Create was given invoice-desk and crash-desk. It printed that the new command loads 2 skills. Neither name was installed. There was no skill directory for either one. Create does not open the skill directory. The number is the length of the list on the bundle that currently owns the slug. If that bundle is the file you just wrote, the number matches the flags you passed. If another file owns the slug, the number matches the other file, and the path in the created-bundle line is a file the command will not load.
Do not use that line as a check that the skills exist. Do not use it as a check that the file you wrote is the file the slash command will read. After create, run show and compare the File line with the path create just printed. If they differ, the force write landed and the command did not move.
Reload reports a scan it just finished
The skills page describes reload as a re-scan that reports changes. On this binary, a new process scans while it is building the command, and reload then diffs that scan against a second scan in the same process. Nothing changed between those two reads. The output, after the colliding files were already on disk, was a no-changes line and a total of 2 bundles. The exit code was 0. The same wording appeared when only desk-route.yaml existed, with a total of 1. Adding a-pack.yaml between two process starts did not produce an added line.
Reload is not a drift report against the previous time you ran it. It is a diff against the scan this process already did. A clean reload does not mean the directory matches what you think is loaded, and it does not mean a hand-edited file was picked up in preference to an older winner. List and show are the check. Reload is not. If you are writing a hook that copies bundle files into the home and then runs reload to prove they were accepted, the hook will pass when the copy was ignored, as long as the process can scan whatever is already there.
Invalid files were quiet in the same way. A YAML file that did not parse, a file whose skills list was empty, and a file whose name was only spaces did not appear in list. Show for empty-pack exited 1 and said the bundle was not found. List still exited 0 and did not name the skipped files. No warning was printed on the terminal. A directory listing is the only place those files showed up. If you are cleaning a bundles directory, list is the loaded set. It is not an inventory of the directory. A broken file can sit beside a working one forever, and neither list nor reload will mention it.
A bundle with nothing to load returns no message
The skills page says a missing member is skipped, not fatal. The bundle still loads the skills that resolve, and the agent gets a note listing what was skipped. It also says a bundle does not install skills for you. Both of those sentences were true for a mixed file. They were not the whole story when every member was missing.
The mixed file listed invoice-desk and missing-desk. invoice-desk was a local skill: a SKILL.md whose name and description were set, and one sentence of body text. missing-desk was a name with no directory. The builder the slash path calls returned a message. The loaded list was invoice-desk. The missing list was missing-desk. The message contained a skipped line naming missing-desk.
That is the note the page describes. It is a note inside a message that also contains the skill that did resolve. It is not a warning from list. List still counted both names. The skill count on the row is the YAML length. It is not the number of directories the builder could open.
The other file listed missing-desk and also-missing. Neither directory existed. List would still have shown the bundle, with a skill count of 2, because list counts the YAML. The builder returned no message. There was no skip note, because there was no message to put it in. A caller that treats “the bundle is in the list” as “the slash command will load guidance” is wrong for this case. The command is registered. The turn content is empty. This run did not start a chat session, so it did not measure how the gateway prints that empty result to a person. It measured the builder the dispatch path calls, on the same checkout, through hermes --run-module. The return value was None.
Keep at least one resolvable skill in a bundle you intend to invoke. A name in the YAML is not that skill. After you write the file, the check is a load, not a list row. If you are shipping a team bundle by dropping YAML into the home, install or copy the skill directories first, then load the bundle once in a disposable home before you treat the command as ready.
Verify the file, then the command
Use a home you can delete. Point HERMES_HOME at it for every command in the check, including the ones that you expect to fail. Do not run the check against the operator home. Create writes into that home, and a force flag overwrites the canonical path even when another file owns the slug.
export HERMES_HOME=<disposable-home>
hermes bundles create yml-only --skill yml-skill -d "canonical"
hermes bundles show yml-only
The File line should end in yml-only.yaml under that home’s skill-bundles directory. If it does, delete of yml-only removes the file show printed, and a second show exits 1. That is the path the help text describes. It is not the path to test if you already have hand-written files.
To see the miss, write a .yml file whose name field is the command, or a .yaml file whose filename sorts before the canonical name and whose name field is the same command. Then show the slug, delete the slug, and show it again. List the filenames in the bundles directory after the delete, not only the command output.
Read the File line before delete. If it does not end in the slug plus .yaml, delete will not remove it. A zero exit means the canonical path was there and is now gone. It does not mean the File line’s path is gone. An exit of 1 means the canonical path was already absent. The command can still be loaded from the path show printed.
Remove the loaded bundle by deleting the path on the File line, then run show again. The command is gone only when show exits 1 and list no longer prints it. Do not stop on the deleted-bundle line. Do not stop on reload. After the file is gone, run the load check if the bundle is supposed to inject a skill. A list count equal to the number of skill flags only tells you that the winning YAML has that many names.
If create’s path and show’s File line disagree, delete the path show printed, not the path create printed. Then show again. If the command is still present, another file still owns the slug. Repeat until show exits 1. Leaving the unused canonical file on disk is harmless only after you have confirmed it is not the file the command loads. On this run, deleting it while a winner remained did not change the command at all.
What you can rely on
On this build, the slash command is the first bundle file the scan kept for that slug. Delete unlinks the canonical yaml path and no other path. Show will tell you when those two files differ. Read that line, delete the path it names, and show the slug again before you treat the command as gone.
Sources
- Hermes Agent v0.22.5+471.g5894e75, commit
5894e750c3db, Python 3.14.9, Linux x86_64, 17 November 2026. List, show, create, delete, and reload ran withHERMES_HOMEset to disposable directories. The load check usedhermes --run-moduleon that checkout. - Skills, skill bundles section, read 17 November 2026. It places bundles at
~/.hermes/skill-bundles/<slug>.yaml, describes delete and reload, and says missing members are skipped with a note. - Hermes Agent v0.23.2, 16 November 2026. This run did not execute that tag. The note does not mention bundle delete.