bundle-builder: generated sub-skills are never registered in Hermes skill system #50

New issue

Closed

opened 2026-05-29 22:54:15 -04:00 by jasper · 0 comments

jasper commented

2026-05-29 22:54:15 -04:00

Contributor

Summary

The workflow-architect bundle-builder generates sub-skill files on disk but never registers them with skill_manage(), so generated skills are invisible to skills_list() and skill_view().

Current Behavior

After convergence, bundle-builder/SKILL.md writes sub-skill .md files to ~/.hermes/skills/<bundle-name>/skills/. Each file has valid Agent Skills frontmatter. But:

The files are named <name>.md, not SKILL.md — Hermes skill discovery requires a SKILL.md at a directory root
The files live in a skills/ subdirectory, not in their own skill directories
No skill_manage(action='create') call registers them in the Hermes skill system
The Cleanup section (step 8) only removes state entries and tells the user where files landed — no registration step exists

The result: after workflow-architect generates a bundle, the user is told "your skills are in this directory" but the agent can't discover or load any of them. The user must manually register each one or manually copy files into the right structure.

Expected Behavior

After writing all bundle files, the agent should register each generated sub-skill so it shows up in skills_list() and can be loaded with skill_view().

Proposed Fix

Add a new "Registration" step to bundle-builder/SKILL.md that, for each generated sub-skill:

Reads the sub-skill .md file content
Calls skill_manage(action='create', name='<bundle-name>-<skill-name>', content=<file-content>, category='generated')

The sub-skill .md files in skills/ already have valid SKILL.md frontmatter (name, description, license, tags) — they're ready to be registered directly.

Why This Matters

This is the missing step that completes the workflow-architect pipeline. Without it, the skill is "generated but invisible" — it exists on disk but the agent can't find it.

Suggested Labels

bug, skill/workflow-architect

## Summary The `workflow-architect` bundle-builder generates sub-skill files on disk but never registers them with `skill_manage()`, so generated skills are invisible to `skills_list()` and `skill_view()`. ## Current Behavior After convergence, `bundle-builder/SKILL.md` writes sub-skill `.md` files to `~/.hermes/skills/<bundle-name>/skills/`. Each file has valid Agent Skills frontmatter. But: 1. The files are named `<name>.md`, not `SKILL.md` — Hermes skill discovery requires a `SKILL.md` at a directory root 2. The files live in a `skills/` subdirectory, not in their own skill directories 3. No `skill_manage(action='create')` call registers them in the Hermes skill system 4. The Cleanup section (step 8) only removes state entries and tells the user where files landed — no registration step exists The result: after workflow-architect generates a bundle, the user is told "your skills are in this directory" but the agent can't discover or load any of them. The user must manually register each one or manually copy files into the right structure. ## Expected Behavior After writing all bundle files, the agent should register each generated sub-skill so it shows up in `skills_list()` and can be loaded with `skill_view()`. ## Proposed Fix Add a new "Registration" step to `bundle-builder/SKILL.md` that, for each generated sub-skill: 1. Reads the sub-skill `.md` file content 2. Calls `skill_manage(action='create', name='<bundle-name>-<skill-name>', content=<file-content>, category='generated')` The sub-skill `.md` files in `skills/` already have valid SKILL.md frontmatter (name, description, license, tags) — they're ready to be registered directly. ## Why This Matters This is the missing step that completes the workflow-architect pipeline. Without it, the skill is "generated but invisible" — it exists on disk but the agent can't find it. ## Suggested Labels bug, skill/workflow-architect