Skill

openrouter-fallback-config

Configure model fallback chains for reliability. Use when building resilient systems that need high availability. Trigger with phrases like 'openrouter fallback', 'model fallback', 'openrouter backup model', 'failover config'.

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/basic-fallback-pattern.md

references/configuration-examples.md

references/error-specific-fallback-logic.md

references/errors.md

references/examples.md

references/fallback-health-tracking.md

references/provider-based-fallback.md

references/smart-fallback-configuration.md

references/task-specific-fallbacks.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

Use OpenRouter's native fallback: Pass an array of model IDs in the models field (instead of model) — OpenRouter will try each in order until one succeeds

Set per-model parameters: Use the route field with "fallback" strategy to let OpenRouter handle failover automatically

Implement client-side fallback: For more control, catch 5xx or timeout errors and retry with the next model in your own fallback list

Configure timeout thresholds: Set request_timeout per attempt so slow models fail fast and the fallback triggers quickly

Test the chain: Temporarily use an invalid model ID as primary to verify your fallback chain activates correctly

Error Handling

Error

Cause

Fix

All fallbacks exhausted

Every model in the chain failed

Add more diverse fallbacks across providers; alert on full chain failure

Slow cascading retries

Each model timing out sequentially

Reduce per-model timeout to 10-15 seconds; use parallel fallback instead

Inconsistent responses

Different models in the chain have different capabilities

Ensure all fallback models support the features your prompt uses (e.g., tool calling)

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

Openrouter Fallback Config

Overview

This skill shows how to configure fallback model chains so requests automatically retry with alternative models when the primary model is unavailable or errors.

Prerequisites

OpenRouter integration
Multiple models identified as primary and fallback options

Instructions

Use OpenRouter's native fallback: Pass an array of model IDs in the models field (instead of model) — OpenRouter will try each in order until one succeeds
Set per-model parameters: Use the route field with "fallback" strategy to let OpenRouter handle failover automatically
Implement client-side fallback: For more control, catch 5xx or timeout errors and retry with the next model in your own fallback list
Configure timeout thresholds: Set request_timeout per attempt so slow models fail fast and the fallback triggers quickly
Test the chain: Temporarily use an invalid model ID as primary to verify your fallback chain activates correctly

Output

A fallback chain that transparently retries with alternative models
Reduced downtime when individual models or providers have outages
Logs showing which model ultimately served each request

Error Handling

Error	Cause	Fix
All fallbacks exhausted	Every model in the chain failed	Add more diverse fallbacks across providers; alert on full chain failure
Slow cascading retries	Each model timing out sequentially	Reduce per-model timeout to 10-15 seconds; use parallel fallback instead
Inconsistent responses	Different models in the chain have different capabilities	Ensure all fallback models support the features your prompt uses (e.g., tool calling)

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

Examples

See ${CLAUDE_SKILL_DIR}/references/examples.md for runnable code samples.

openrouter-fallback-config

openrouter-fallback-config

Openrouter Fallback Config

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources

Openrouter Fallback Config

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources