Cairn
NousResearch/hermes-agent

Skill load errors returning stub instead of None

Cluster 11200 · skills. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where skill load errors return a truthy stub or sentinel value instead of None, causing the errors to be mishandled as successful invocations or queued as input. Multiple corrections and related reports address this same incorrect return value behavior.

Open issues0

No open issues.

Open PRs0

No open pull requests.

5 PRs closed without merging

From the close comments: done elsewhere 2 · duplicate 2 · superseded by another PR 1

  • #11380 fix(skills): treat slash-command load failures explicitly · done elsewhere → 4b17c24
  • #11408 fix(skills): surface skill-load failures instead of returning success · duplicate → #14752, #11200, #14713
  • #11545 Treat failed skill loads as actual command failures · duplicate → #11200, #11380, #11408
  • #14752 fix: skill load failures return None instead of queued sentinel (#14713) · done elsewhere
  • #17330 fix(skills): return None instead of truthy stub when skill load fails (#17283) · superseded by another PR → #14752, #14713
Closed issues · 3
  • Closed#11200[Bug]: Skill load failure is treated as successful slash-command invocation
  • Closed#14713Slash-skill load failures are queued as input instead of surfacing an error
  • Closed#17283[Bug]: Webhook gateway — skill auto-loader returns 'Failed to load skill' stub instead of None, silently dropping user prompt after extended uptime
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.22: 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
skills
Closed issues
3
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/11200.json
cluster/11200.md