Cairn
NousResearch/hermes-agent

Per-skill model or provider selection for skills

Cluster 5997 · skills. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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.

All three members concern choosing or overriding the LLM model on a per-skill basis. They differ in approach: one proposes routing through delegate_task, one is a general feature request for switching models by skill, and one proposes SKILL.md frontmatter overrides.

Open issues0

No open issues.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: other 1

  • #19270 feat: per-skill model/provider override via SKILL.md frontmatter · other
Closed issues · 2
  • Closed#5997[Feature]: LLM model switch by skill
  • Closed#42146feat: mandatory per-skill model routing via delegate_task
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.45: 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
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/5997.json
cluster/5997.md