NousResearch/hermes-agent

Skill lookup by frontmatter name versus directory slug

Cluster 61172 · dashboard. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #133967 on 6 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #133967. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #133967. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #133967, then check it covers your case.

Read #133967 Pick up a Lab task

These members all concern skills not being found or opened when the frontmatter display name differs from the directory slug, affecting _find_skill() in the skill manager and the dashboard skill editor. Three are fix-oriented changes and one is a bug report; their titles do not show whether any fix has been merged or works.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#133967 fix(skills): resolve skills by frontmatter display name in the manager and dashboard editor

merged to main

files: tests/hermes_cli/test_web_server_skill_editor.py, tests/tools/test_skill_manager_tool.py, tools/skill_manager_tool.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#61177 fix(tools/skill_manager): support frontmatter.name in _find_skill() (#61172) · superseded by another PR → #99626, #61172
#99626 fix(skills): resolve the frontmatter name _find_skill ignores · merged via another change

Closed issues · 1

Closed#61172[Bug]: Dashboard Skill Editor cannot open skills when display name differs from directory slug

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: dashboard
Merged PRs: #133967
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 6 Oct 2026

For your agent

The same facts, typed.

cluster/61172.json
cluster/61172.md