router-template
Template for creating router skills. Use as a starting point when building a new router that dispatches to multiple specialized skills. Copy and customize for your domain.
When & Why to Use This Skill
This Claude skill provides a standardized template for building intelligent router agents that efficiently dispatch complex tasks to specialized sub-skills. It streamlines agent orchestration by implementing a robust routing protocol, including task classification, signal matching, and multi-skill combination strategies to ensure high-precision task execution and optimized AI workflows.
Use Cases
- Architecting Multi-Agent Systems: Serve as the central dispatching layer to route user requests to specific domain experts like frontend, backend, or database specialists.
- Framework-Specific Coding Assistants: Automatically identify and trigger specialized skills for React, Vue, or Vanilla JS based on the detected project context and signal words.
- Complex Workflow Integration: Orchestrate tasks that require the combined output of 2-4 specialized skills, such as performing web research followed by technical writing and SEO optimization.
- Intelligent Task Triage: Implement confidence scoring to determine whether to route a task immediately, use default settings, or ask the user for further clarification.
| name | router-template |
|---|---|
| description | Template for creating router skills. Use as a starting point when building a new router that dispatches to multiple specialized skills. Copy and customize for your domain. |
[Domain] Router
Routes to N specialized skills based on task requirements.
Routing Protocol
- Classify — Identify primary task type from user request
- Match — Find skill(s) with highest signal match
- Combine — Most production tasks need 2-4 skills together
- Load — Read matched SKILL.md files before implementation
Quick Route
Tier 1: Core (Always Consider)
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| [task] | skill-name |
word1, word2, word3 |
Tier 2: Enhanced (Add When Needed)
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| [task] | skill-name |
word1, word2, word3 |
Tier 3: Reference Only
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| [task] | skill-name |
word1, word2, word3 |
Signal Matching Rules
Priority Order
When multiple signals present, resolve by priority:
- Explicit framework — React/Vue/vanilla overrides generic signals
- Specific feature — "multi-step wizard" beats generic "form"
- Platform constraint — mobile/VR/accessibility takes precedence
- Default tier — Fall back to Tier 1 core skills
Confidence Scoring
- High (3+ signals) — Route immediately
- Medium (1-2 signals) — Route with Tier 1 defaults
- Low (0 signals) — Ask user for clarification
Common Combinations
[Scenario Name] (N skills)
skill-1 → [what it provides]
skill-2 → [what it provides]
skill-3 → [what it provides]
Wiring: [one-line integration summary]
[Scenario Name] (N skills)
skill-1 → [what it provides]
skill-2 → [what it provides]
Wiring: [one-line integration summary]
Decision Table
| Framework | Scale | Features | Route To |
|---|---|---|---|
| React | Standard | Auth form | skill-a + skill-b + skill-c |
| Vue | Standard | Data entry | skill-a + skill-d |
| None | Simple | Basic form | skill-e + skill-b |
| Any | Complex | Wizard | skill-f + skill-a + skill-b |
Fallback Behavior
- Unknown framework → Use skill with broadest compatibility
- No clear signals → Ask: "What framework?" and "What's the core requirement?"
- Conflicting signals → Prefer Tier 1 skills, ask for clarification on Tier 2
Reference
See references/integration-guide.md for:
- Complete wiring patterns
- Code examples for all combinations
- Architecture diagrams
- Edge case handling