
Router Template
- 53 installs
- 8 repo stars
- Updated August 4, 2026
- bbeierle12/skill-mcp-claude
router-template is a Claude skill that provides a reusable template for creating router skills that dispatch tasks to multiple specialized skills.
About
This skill is a starting-point template for building new router skills that dispatch to multiple specialized skills. It provides the standard scaffolding: a routing protocol, tiered quick-route tables, signal-matching rules, confidence scoring, and fallback behavior. A developer copies and customizes it when creating a router for their own domain.
- Reusable template for building router skills that dispatch to multiple specialized skills
- Includes routing protocol, signal-matching rules, confidence scoring, and a decision table
- Meant to be copied and customized for a new domain
Router Template by the numbers
- 53 all-time installs (skills.sh)
- Ranked #320 of 782 Skill Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
router-template capabilities & compatibility
- Capabilities
- skill creator · shader router
- Use cases
- orchestration
What router-template says it does
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.
Routes to N specialized skills based on task requirements.
Most production tasks need 2-4 skills together
npx skills add https://github.com/bbeierle12/skill-mcp-claude --skill router-templateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 53 |
|---|---|
| repo stars | ★ 8 |
| Last updated | August 4, 2026 |
| Repository | bbeierle12/skill-mcp-claude ↗ |
What it does
Scaffold a new router skill that dispatches to specialized skills for a domain.
Who is it for?
Kicking off a new router skill for a specific domain.
When should I use this skill?
Building a new router that dispatches to multiple specialized skills.
What you get
- A customized router SKILL.md for a chosen domain
By the numbers
- Ships tiered quick-route tables across 3 tiers (Core, Enhanced, Reference Only)
Files
[Domain] Router
Routes to N specialized skills based on task requirements.
Routing Protocol
1. Classify — Identify primary task type from user request 2. Match — Find skill(s) with highest signal match 3. Combine — Most production tasks need 2-4 skills together 4. 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: 1. Explicit framework — React/Vue/vanilla overrides generic signals 2. Specific feature — "multi-step wizard" beats generic "form" 3. Platform constraint — mobile/VR/accessibility takes precedence 4. 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
{
"name": "router-template",
"description": "Template for creating router skills that classify user requests and dispatch to specialized sub-skills based on task type and requirements.",
"tags": [
"meta-tooling",
"scaffolding"
],
"sub_skills": [],
"source": "claude-user",
"type": "template",
"depends_on": [],
"enhances": [
"skill-creator"
],
"last_reviewed_at": null,
"review_score": null,
"relevance_tier": null
}