skill-router

Select the best matching skill using trigger labels, file-path signals, and keyword overlap.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/jacob-balslev/skill-graph --skill skill-router-jacob-balslev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-router
Source: https://github.com/jacob-balslev/skill-graph/tree/main/marketplace/skills/skill-router
Command: npx skills add https://github.com/jacob-balslev/skill-graph --skill skill-router-jacob-balslev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Skill-router prevents mis-dispatch by deterministically choosing the correct skill for an incoming agent request, or surfacing an explicit coverage gap when nothing matches.

Core Features & Use Cases

  • Priority-ordered routing: Selects a unique match using trigger labels first, then file-path signals, then keyword pattern overlap.
  • Specificity tiebreakers: Uses scope and type rules to break score ties without relying on popularity or randomness.
  • Coverage-gap detection: Refuses silent fallback when no skill matches, prompting authors to add triggers/paths/keywords.

Quick Start

Ask the agent to decide which skill should handle a user request, and the router will return the winning skill selection or a coverage-gap signal when no match exists.

Frequently Asked Questions about skill-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route agent requests to the correct skill without mis-dispatching?

Agent request routing uses trigger labels, file-path signals, and keyword overlap to deterministically match requests to the correct skill, preventing confident misrouting. It selects a unique match by applying priority ordering and specificity tiebreakers.

What happens when no skill matches an incoming agent request?

When no skill matches an agent request, the routing returns an explicit coverage-gap signal instead of a silent fallback. This prompts skill authors to add missing triggers, file paths, or keywords to close the gap.

How are scoring ties broken when multiple skills match a request?

Scoring ties are broken using scope and type rules to ensure deterministic priority ordering. This avoids relying on popularity or randomness when selecting the best matching skill for a request.

How do I audit and debug routing coverage gaps in a multi-skill library?

Auditing routing coverage gaps in a multi-skill library evaluates trigger labels and keyword overlap to identify unmatched requests. It generates coverage-gap reports consistent with repository evaluation artifacts for debugging.

What is the best way to build a routing table for multiple agent skills?

Building a routing table for multiple agent skills applies deterministic priority ordering across trigger labels, file-path signals, and keyword overlap. This creates a structured map ensuring accurate request dispatch.