Route Claude Code requests across models and providers with Claude Code Router
Run Claude Code through Claude Code Router to route coding-agent requests by task, provider, or model while preserving terminal workflows and adding provider-specific transformations.
npx skills add agentskillexchange/skills --skill route-claude-code-requests-across-models-and-providers-with-claude-code-router
Claude Code Router is a terminal workflow layer for routing Claude Code traffic to different models and providers. Use this skill when an operator wants Claude Code as the interface but needs explicit routing for background tasks, long-context work, thinking-heavy tasks, fallback providers, GitHub Actions, or provider-specific request and response transformations.
What this skill actually does
The workflow is to install Claude Code and Claude Code Router, define providers and routing rules in the router config, start the router, and use Claude Code normally while switching models or letting configured routes handle requests. The scope boundary is coding-agent model/provider routing for Claude Code sessions; it is not a generic proxy, model marketplace, or standalone LLM gateway listing.
Inputs and prerequisites: Claude Code; Node.js/npm; one or more model provider API keys or local provider endpoints.
Setup notes: Install Claude Code, then install with `npm install -g @musistudio/claude-code-router`; create `~/.claude-code-router/config.json` with providers, models, transformers, and routing rules before running Claude Code through the router.
Source and verification boundary: use https://github.com/musistudio/claude-code-router as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Claude Code workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.