llm

Route prompts to multiple LLM providers with configurable routing rules.

2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ZealousEar/claude-skills --skill llm-zealousear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm
Source: https://github.com/ZealousEar/claude-skills/tree/main/claude-code/llm
Command: npx skills add https://github.com/ZealousEar/claude-skills --skill llm-zealousear

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Route prompts to multiple providers from a single interface, enabling cross-model comparisons and guardrail enforcement. The system supports CLI-first routing for Claude Code, Codex, and Kimi, and API-based routing for Google, OpenRouter, and Anthropic models, with auto-discovery of new models. It relies on a local registry, per-model prompting overrides, and routing rules to deterministically select providers and gracefully fall back when needed.

Core Features & Use Cases

  • Unified LLM routing: send prompts to Claude, OpenAI, Google, Moonshot, and other APIs from a single interface, with CLI-first routing for certain models and API routing for others.
  • Auto-discovery & routing: automatically discover new models and route them using configurable routing rules, with per-model prompting overrides.
  • Deterministic execution & guardrails: deterministic task execution via scripts and structured routing that supports fallback when needed.

Quick Start

Prompt the router to send a query to a chosen model (e.g., gpt-5.3-codex) and return its response.

Frequently Asked Questions about llm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route prompts to multiple LLM providers from a single interface?

You can route prompts to multiple LLM providers from a single interface by using configurable routing rules, per-model prompting overrides, and a local registry to deterministically select providers and gracefully fall back when needed.

How does multi-provider LLM routing handle fallback when a model fails?

Multi-provider LLM routing handles fallback by using deterministic routing rules that gracefully shift execution to alternative models when the primary provider fails, ensuring task completion.

Can I use CLI-first routing for Claude Code and Codex alongside API routing for Google and OpenRouter?

Yes, you can use CLI-first routing for Claude Code, Codex, and Kimi alongside API-based routing for Google, OpenRouter, and Anthropic models, with auto-discovery of new models.

How do I enforce guardrails and apply per-model prompting overrides across different models?

You enforce guardrails and apply per-model prompting overrides across different models by relying on deterministic task execution via scripts and structured routing rules within the unified interface.

What is the best way to compare responses across different LLM models?

The best way to compare responses across different LLM models is to use a unified routing interface that sends identical prompts to multiple providers, enabling direct cross-model comparisons.

Does multi-provider LLM routing support auto-discovery of new models?

Yes, multi-provider LLM routing supports auto-discovery of new models, automatically registering them in the local registry for immediate use with existing routing rules and overrides.