Skill

openrouter-multi-provider

Use multiple AI providers through OpenRouter. Use when leveraging different providers for different capabilities. Trigger with phrases like 'openrouter providers', 'multi provider', 'openrouter openai anthropic', 'use multiple models'.

From openrouter-pack

Install

Run in your terminal

npx claudepluginhub nickloveinvesting/nick-love-plugins --plugin openrouter-pack

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGrep

Supporting Assets

View in Repository

references/cost-optimization-across-providers.md

references/errors.md

references/examples.md

references/model-comparison.md

references/multi-provider-router.md

references/provider-fallback-chain.md

references/provider-health-monitoring.md

references/provider-overview.md

references/provider-specific-features.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Instructions

Understand the provider namespace: OpenRouter model IDs use provider/model-name format (e.g., openai/gpt-4-turbo, anthropic/claude-3.5-sonnet, google/gemini-pro)

Compare provider strengths: Test the same prompt across providers to evaluate quality, speed, and cost; each provider excels at different task types

Route by task type: Use OpenAI models for code generation, Anthropic for analysis and safety, Google for multimodal, and open-source models for cost-sensitive tasks

Handle provider-specific features: Some features (like system prompts, tool calling, or JSON mode) work differently across providers; test each model's behavior

Build a provider abstraction: Create a thin wrapper that normalizes provider differences so your application code doesn't need to know which provider is serving the request

Error Handling

Error	Cause	Fix
Feature not supported	Provider doesn't support the requested feature (e.g., tools)	Check model capabilities via `/models` endpoint before sending
Different response formats	Providers return slightly different structures	Normalize responses through your abstraction layer
Provider outage	Single provider is down	Implement cross-provider fallback (e.g., OpenAI -> Anthropic -> Google)

Error

Cause

Fix

Feature not supported

Provider doesn't support the requested feature (e.g., tools)

Check model capabilities via /models endpoint before sending

Different response formats

Providers return slightly different structures

Normalize responses through your abstraction layer

Provider outage

Single provider is down

Implement cross-provider fallback (e.g., OpenAI -> Anthropic -> Google)

See ${CLAUDE_SKILL_DIR}/references/errors.md for full error reference.

Instructions

Understand the provider namespace: OpenRouter model IDs use provider/model-name format (e.g., openai/gpt-4-turbo, anthropic/claude-3.5-sonnet, google/gemini-pro)

Compare provider strengths: Test the same prompt across providers to evaluate quality, speed, and cost; each provider excels at different task types

Route by task type: Use OpenAI models for code generation, Anthropic for analysis and safety, Google for multimodal, and open-source models for cost-sensitive tasks

Handle provider-specific features: Some features (like system prompts, tool calling, or JSON mode) work differently across providers; test each model's behavior

Build a provider abstraction: Create a thin wrapper that normalizes provider differences so your application code doesn't need to know which provider is serving the request

Error Handling

Error	Cause	Fix
Feature not supported	Provider doesn't support the requested feature (e.g., tools)	Check model capabilities via `/models` endpoint before sending
Different response formats	Providers return slightly different structures	Normalize responses through your abstraction layer
Provider outage	Single provider is down	Implement cross-provider fallback (e.g., OpenAI -> Anthropic -> Google)

Error

Cause

Fix

Feature not supported

Provider doesn't support the requested feature (e.g., tools)

Check model capabilities via /models endpoint before sending

Different response formats

Providers return slightly different structures

Normalize responses through your abstraction layer

Provider outage

Single provider is down

Implement cross-provider fallback (e.g., OpenAI -> Anthropic -> Google)

See ${CLAUDE_SKILL_DIR}/references/errors.md for full error reference.

openrouter-multi-provider

openrouter-multi-provider

Openrouter Multi Provider

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources

Openrouter Multi Provider

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources