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.

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 30, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a professional-grade template for building router agents designed to orchestrate and dispatch tasks across multiple specialized skills. It establishes a robust framework for intent classification, signal matching, and multi-tool integration, ensuring that complex user requests are handled by the most relevant combination of sub-skills for optimal performance and accuracy.

Use Cases

  • Case 1: Architecting a complex software engineering agent that needs to intelligently route tasks between specialized skills for UI design, API development, and unit testing.
  • Case 2: Developing a versatile customer operations bot that classifies incoming queries to trigger specific workflows for billing, technical support, or account security.
  • Case 3: Creating a multi-step research pipeline that dynamically combines web search, document analysis, and data visualization tools based on the depth of the user's inquiry.
  • Case 4: Building a project management assistant that switches between scheduling, resource allocation, and reporting skills depending on the project lifecycle stage.
namerouter-template
descriptionTemplate 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

  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