{"repo":"NousResearch/hermes-agent","public_id":"5997","display_label":"Per-skill model or provider selection for skills","summary":"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.","subsystem":"skills","counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":2,"merged_prs":0,"attempt_prs":1},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_PARTIAL","link_density":0.4533333333333333},"fix_edges":[],"members":[{"kind":"issue","number":5997,"title":"[Feature]: LLM model switch by skill","url":null,"state":"closed"},{"kind":"issue","number":42146,"title":"feat: mandatory per-skill model routing via delegate_task","url":null,"state":"closed"},{"kind":"pr","number":19270,"title":"feat: per-skill model/provider override via SKILL.md frontmatter","url":null,"state":"closed","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}