Agent skill · AI & Agents

llm-router

This skill should be used when users want to route LLM requests to different AI providers (OpenAI, Grok/xAI, Groq, DeepSeek, OpenRouter) using SwiftOpenAI-CLI. Use this skill when users ask to "use grok", "ask grok", "use groq", "ask deepseek", or any similar request to query a specific LLM provider in agent mode.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill llm-router --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 13 KB
Bundled scripts: none
Path: skills/ai-llm/llm-router/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# LLM Router ## Overview Route AI requests to different LLM providers using SwiftOpenAI-CLI's agent mode. This skill automatically configures the CLI to use the requested provider (OpenAI, Grok, Groq, DeepSeek, or OpenRouter), ensures the tool is installed and up-to-date, and executes one-shot agentic tasks. ## Core Workflow When a user requests to use a specific LLM provider (e.g., "use grok to explain quantum computing"), follow this workflow: ### Step 1: Ensure SwiftOpenAI-CLI is Ready Check if SwiftOpenAI-CLI is installed and up-to-date: ```bash scripts/check_install_cli.sh ``` This script will: - Check if `swiftopenai` is installed - Verify the version (minimum 1.4.4) - Install or update if necessary - Report the current installation status ### Step 2: Configure the Provider Based on the user's request, identify the target provider and configure SwiftOpenAI-CLI: ```bash scripts/configure_provider.sh <provider> [model] ``` **Supported providers:** - `openai` - OpenAI (GPT-4, GPT-5, etc.) - `grok` - xAI Grok models - `groq` - Groq (Llama, Mixtral, etc.) - `deepseek` - DeepSeek models - `openrouter` - OpenRouter (300+ models) **Examples:** ```bash # Configure for Grok scripts/con

What's inside
Steps it walks through
  1. Overview
  2. Core Workflow
  3. Step 1: Ensure SwiftOpenAI-CLI is Ready
  4. Step 2: Configure the Provider
  5. Step 3: Verify API Key
  6. Step 4: Execute the Agentic Task
  7. Usage Patterns
  8. Pattern 1: Simple Provider Routing
  9. Pattern 2: Specific Model Selection
  10. Pattern 3: Fast Inference with Groq
  11. Pattern 4: Access Multiple Models via OpenRouter
  12. Provider-Specific Considerations
  13. OpenAI (GPT-5 Models)
  14. Grok (xAI)
Ships with 1 file
  • metadata.json
Commands it runs
scripts/check_install_cli.sh
scripts/configure_provider.sh <provider> [model]
Configure for Grok
scripts/configure_provider.sh grok grok-4-0709
Configure for Groq with Llama
scripts/configure_provider.sh groq llama-3.3-70b-versatile
Configure for DeepSeek Reasoner
scripts/configure_provider.sh deepseek deepseek-reasoner
Configure for OpenAI GPT-5
scripts/configure_provider.sh openai gpt-5
More from claude-skill-registry
All skills →
About this skill
What does the llm-router skill do?

This skill should be used when users want to route LLM requests to different AI providers (OpenAI, Grok/xAI, Groq, DeepSeek, OpenRouter) using SwiftOpenAI-CLI. Use this skill when users ask to "use grok", "ask grok", "use groq", "ask deepseek", or any similar request to query a specific LLM provider in agent mode.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill llm-router --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going