NousResearch/hermes-agent

Curator pin misleading success on unmanaged skills

Cluster 92993. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #93486 on 24 Aug 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 #93486. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #93486. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #93486 Pick up a Lab task

These issues and PRs address a bug where the Hermes curator pin command falsely reports success for unmanaged skills, while the pin remains invisible in curator status output. The work focuses on correcting the reported behavior and messaging to accurately reflect what pin does in this case.

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.

#93486 curator pin no longer claims success on unmanaged skills (#92993, salvage #93149 + #93002)

merged to main

files: contributors/emails/[email protected], hermes_cli/curator.py, tests/hermes_cli/test_curator_pin_unmanaged.py, tests/hermes_cli/test_curator_pin_visibility.py, tools/skill_usage.py

2 PRs closed without merging

From the close comments: merged via another change 2

#93002 fix(curator): say what pin actually does on an unmanaged skill · merged via another change → 95af454, #93486, #93149
#93149 fix(curator): report pin failures instead of false success and surface pinned unmanaged skills · merged via another change → 95af454, #93486, #93002

Closed issues · 1

Closed#92993hermes curator pin prints success on unmanaged skills but the pin is invisible to 'hermes curator status'

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

Merged PRs: #93486
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 24 Aug 2026

For your agent

The same facts, typed.

cluster/92993.json
cluster/92993.md