references/example-router-skill.md
Case Study: Router Skill Synthesis
Scenario
Goal: create a skill that classifies requests into distinct downstream paths without overloading one prompt.
Input collection approach
This case collected:
- examples of request categories
- known ambiguous cases
- downstream resources for each route
- historical misroutes and their fixes
Collection stopped only after route criteria and fallback behavior were explicit.
Coverage matrix used
Required dimensions tracked during synthesis:
- route categories and triggers
- ambiguous or overlapping cases
- downstream ownership per route
- default/fallback path
- misroute recovery behavior
Synthesized artifacts produced
The resulting skill references included:
- route-selection table
- one reference or script per route
- ambiguous-case examples
- fallback rule for unclear input
What made this high quality
- the route table was explicit
- every route had one clear downstream owner
- the skill knew what to do when classification was uncertain