Cairn

Skills tap search, inspect, and resolution bugs

NousResearch/hermes-agent · cluster 14290 · hermes cli

Data as of

6 open items. Fix attempted, not merged.

The short answer

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

Multiple issues and fixes addressing problems where skills in custom or local taps were not found, not searched, or not inspected correctly. Covers gaps in tap-aware search, inspect resolution order, and validation of unsupported tap repositories.

Open issues3

  • Issue#14290skills tap add accepts custom git repos that search/install cannot actually use
  • Issue#14466[Bug]: Skills in a tap are not found
  • Issue#25087[Bug]: hermes skills inspect fails for installed local skills with misleading 'not found' error

Open PRs3

  • PR#14299fix(skills): reject unsupported tap repositories
  • PR#14416fix(skills): reject unsupported custom taps
  • PR#58235fix(skills): include user taps in default search

4 PRs closed without merging

From the close comments: PR volume cleanup 1 · duplicate 1 · stale or abandoned 1 · superseded by another PR 1

  • #14475 fix(skills): search custom taps when index is enabled · stale or abandoned
  • #25153 fix(skills): inspect local/installed skills instead of only querying hub registries · superseded by another PR → #24513
  • #25179 fix(cli): inspect local skills when not found in hub sources · duplicate → #24513, #25153, #25087
  • #31888 fix(skills): resolve inspect against installed local skills before hub · PR volume cleanup
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.17: 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
Closed issues
0
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/14290.json
cluster/14290.md