Dynamic Skill Router

The problem

When an agent workspace contains skills for multiple platforms and tasks, the model may not know which skill should handle the current request. Guessing by name can miss project-level skills, skipping frontmatter can misread triggers, and loading without verification can send work to the wrong capability.

How it works

skill-router-dynamic is a meta-routing skill that does not perform domain work itself. It routes requests to the correct SKILL.md. Its lifecycle includes:
- Entry Guard: decide whether the message is chat or a task, avoiding unnecessary routing.
- Scan: check project-level and user-level skill directories in priority order, then extract name, description, and triggers.
- Match: choose direct loading, present options, or report missing skills based on confidence.
- Verify: check whether the executed skill produced an on-intent result, and return to scanning on failure.
- Control Hook: keep the loaded skill in the same session, while new sessions re-enter routing.
Key outputs use the [skill-router] prefix so routing events can be searched in transcripts. Multi-skill patterns support sequential, parallel, and composed workflows, with context passed step by step.

Boundaries

It assumes readable SKILL.md files and conventional directories, so it is not a substitute for loose prompt files without frontmatter. Logging is opt-in and local by design. Routing quality still depends on how clearly candidate skills describe their purpose.