
from skill-router37
Decides when to route a request to a different skill versus executing directly; prevents wasteful discovery or unnecessary installations.
Skill Router helps agents decide whether to route a user request to another installed skill, discover new skills, or just execute the task directly. It focuses only on decisions where the choice of skill materially changes the next action, reducing repeated discovery, unnecessary installs, and lengthy routing commentary. The skill provides a clear decision path: check installed capabilities, test for insufficiency, limit discovery to real gaps, and vet unfamiliar candidates before recommending installation.
Use Skill Router when the user explicitly asks which skill to use, whether a suitable skill is already installed, or when multiple installed skills plausibly fit and the default is unclear. Do not use for straightforward single-skill matches or simple execution tasks. Prefer silence if routing would not change the next action.
Best for agents that can inspect installed skills and run discovery helpers (Claude Code, Copilot-style agents, CLI-based orchestrators).
Skill Router is a pure-instruction skill that guides agents on when to route requests to other skills vs executing directly. No scripts included — entirely declarative SKILL.md with clear trigger boundaries, a 5-step decision path, and concise output shapes. Clean security profile with no executable code. Architecture follows skill spec conventions with references/ directory and progressive disclosure. Niche usefulness — overlaps with built-in agent skill-matching logic.
Clean skill with no security concerns. Duplicate last paragraph in SKILL.md body (likely copy-paste artifact). Skill is well-structured but its value proposition is narrow — most agent runtimes already handle skill routing internally.