NousResearch/hermes-agent

Curator status labeling of skills as agent-created

Cluster 64393 · hermes cli. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #71648 on 26 Jul 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 #71648. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #71648 Pick up a Lab task

Members center on the curator's status output labeling skills, with a bug report (#64393) saying bundled prune candidates appear as "agent-created" and two pull requests proposing relabeling or label fixes. A fourth member adds a related but distinct feature to surface unmanaged skills and a curator adopt command.

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.

#71648 feat(curator): surface unmanaged skills and add `curator adopt`

merged to main

files: agent/curator.py, hermes_cli/curator.py, tests/hermes_cli/test_curator_archive_prune.py, tests/hermes_cli/test_curator_status.py, tests/tools/test_skill_usage.py, tests/tools/test_skills_sync.py, tools/skill_usage.py, tools/skills_sync.py, website/docs/user-guide/features/curator.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

#64452 fix: curator labels bundled skills as agent-created (#64393) · merged via another change → b9fedab, #71648
#64479 fix(#64393): relabel curator status from "agent-created" to "curator-managed skills" · done elsewhere → #64393, #71648, #64452

Closed issues · 1

Closed#64393[Bug]: curator status labels bundled prune candidates as agent-created skills

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: hermes cli
Merged PRs: #71648
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 26 Jul 2026

For your agent

The same facts, typed.

cluster/64393.json
cluster/64393.md