- Home
- Skills
- Bbeierle12
- Skill Mcp Claude
- Router Template
router-template_skill
- JavaScript
6
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill bbeierle12/skill-mcp-claude --skill router-template- _meta.json351 B
- SKILL.md2.7 KB
Overview
This skill is a router template that dispatches requests to multiple specialized skills. It provides a lightweight protocol for classifying requests, matching relevant skills, and combining them into a multi-skill workflow. Use it as a starting point to build a domain-specific router that coordinates 2–4 skills per task.
How this skill works
The router classifies the user request to identify the primary task type, then scores available skills by signal match. It applies priority rules to resolve conflicting signals, selects the highest-confidence skills, and recommends combinations for production tasks. When signals are weak, the router prompts for clarification to improve routing accuracy.
When to use it
- Building a coordinator that dispatches work across multiple specialized skills
- When tasks require combining 2–4 capabilities (e.g., UI, validation, auth)
- When you need a repeatable protocol for classifying and scoring requests
- Integrating domain-specific skills with clear precedence and fallback rules
- Rapidly scaffolding new routers for different application frameworks
Best practices
- Define clear signal keywords for each skill and group them into tiers
- Prioritize explicit framework and platform constraints over generic signals
- Combine complementary skills for production flows rather than single-skill answers
- Implement a confidence threshold: route immediately for high scores, ask for clarification for low scores
- Keep wiring patterns small and documented so combinations are predictable
Example use cases
- Web form builder: classify form type, attach validation, UI rendering, and auth skills
- Multi-platform feature: prefer mobile-optimized skills when a mobile signal is present
- Complex wizard: route to orchestration, state management, and UI stepper skills
- Quick prototype: use Tier 1 core skills as defaults, then add Tier 2 enhancements
- Fallback handling: detect unknown frameworks and route to the broadest-compatible skill
FAQ
Most production tasks combine 2–4 skills: one for core functionality, one or two for features, and one for integration or platform concerns.
What if multiple signals conflict?
Resolve by priority: explicit framework > specific feature > platform constraint > default tier. If still ambiguous, prefer core skills and ask the user a clarifying question.