Classify the work before choosing tools
The router first separates task nature, work stage, and technical domain so the agent does not treat every request as generic implementation work.
Turn each Codex request into a small, reviewable SKILL route before files change.
Fix the homepage Hero so first-time users understand this SKILL.
design-taste-frontend
ui-ux-pro-max
Clarify first impression, then check responsive readability.
Selects SKILLs only. Tool permissions stay external.
Most agents do not fail because they lack tools. They fail because every related workflow competes for attention. This router turns task intent into a small, reviewable skill set before execution starts, then leaves authorization and approval to your existing governance layers.
Read the customization guideThe router first separates task nature, work stage, and technical domain so the agent does not treat every request as generic implementation work.
A Primary skill owns the main reasoning path. Supporting skills can help, but they should not compete for control of the task.
Routes stay small: usually one Primary skill plus one to three Supporting skills for APIs, databases, browser checks, docs, CI, or release work.
Instead of asking the agent to remember every workflow at once, the user sees a short routing contract and can correct it before files are edited.
The example is no longer a second product to choose. It shows one public-safe catalog so readers can learn the structure, then adapt Blank Router to their own skills.
Explore Reference TemplateReaders no longer need to choose between several scenario pages. This catalog turns the template zip skills into copyable routes.
Database / Performance / Slow query
Primary: database-optimizer
Supporting: sql-pro, systematic-debugging System, planning, architecture, API, backend, database, frontend, docs, DevOps, brand, and product skills.
Practical route catalogRoutes are grouped by real engineering categories with one Primary skill and focused Supporting skills.
Source-first proofEvery section links back to the GitHub folder and the exact sample route files behind the site.
A route is narrow enough for the user to correct before the agent edits files.
A new user can download the template, inspect the catalog, and adapt routes to their own agent environment.
Public examples stay generic while private overlays can keep organization-specific rules local.
The proof flow checks router structure, scans the sample skill catalog, validates public route cases, evaluates route quality, and runs the unit tests before the repo is shared.
# 1. Validate router structure
python scripts/validate-router.py starter/workflow-skill-router
python scripts/validate-router.py examples/template-skill-catalog
# 2. Scan skill catalog
python scripts/scan-skills.py ./sample-skills \
--out /tmp/skill-index.json \
--markdown /tmp/skill-index.md \
--warnings /tmp/skill-warnings.md \
--suggest-tree /tmp/suggested-skill-tree.md \
--fail-on-private \
--fail-on-duplicates
# 3. Evaluate routing quality
python scripts/evaluate-routing.py \
--scenarios evaluation/scenarios.example.jsonl \
--predictions evaluation/predictions.example.jsonl \
--report /tmp/routing-report.md \
--json-report /tmp/routing-report.json \
--fail-on-violations \
--strict
python -m unittest discover -s tests View validation toolchain Open the repository, inspect the starter, and follow releases if the pattern fits your agent workflow.