Skill

openrouter-routing-rules

Define custom routing rules for OpenRouter requests. Use when implementing complex routing logic beyond simple model selection. Trigger with phrases like 'openrouter rules', 'routing rules', 'custom routing', 'openrouter request routing'.

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-routing-strategies.md

references/cost-aware-routing.md

references/errors.md

references/examples.md

references/implementation.md

references/latency-aware-routing.md

references/rule-based-router.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

Define routing dimensions: Identify the factors that should influence model selection — user tier (free/paid), task type (chat/code/analysis), cost budget, latency requirement

Build a rules engine: Create a configuration-driven rules engine where each rule has conditions (e.g., user.tier == "free") and actions (e.g., model = "google/gemma-2-9b-it:free")

Implement rule evaluation: Process rules in priority order; the first matching rule determines the model; always include a default/catch-all rule

Add dynamic rules: Support rules that query real-time data (current cost, model availability, error rates) to make routing decisions

Test with rule scenarios: Write test cases for each rule to verify correct model selection under different conditions

Error Handling

Error

Cause

Fix

No rule matched

Conditions don't cover all cases

Always include a default catch-all rule at the end

Rule evaluation error

Dynamic rule query failed (e.g., cost API timeout)

Add fallback values for dynamic data; never block on rule evaluation

Wrong model selected

Rule priority order incorrect

Add logging to show which rule matched and why; review priority ordering

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

Openrouter Routing Rules

Overview

This skill shows how to implement rule-based routing that dynamically selects models based on prompt content, user tier, cost constraints, or time-of-day patterns.

Prerequisites

OpenRouter integration with multiple models configured
Routing requirements defined (by user tier, task type, cost, etc.)

Instructions

Define routing dimensions: Identify the factors that should influence model selection — user tier (free/paid), task type (chat/code/analysis), cost budget, latency requirement
Build a rules engine: Create a configuration-driven rules engine where each rule has conditions (e.g., user.tier == "free") and actions (e.g., model = "google/gemma-2-9b-it:free")
Implement rule evaluation: Process rules in priority order; the first matching rule determines the model; always include a default/catch-all rule
Add dynamic rules: Support rules that query real-time data (current cost, model availability, error rates) to make routing decisions
Test with rule scenarios: Write test cases for each rule to verify correct model selection under different conditions

Output

A configurable rules engine that selects models based on multiple dimensions
Rule configuration file (JSON/YAML) that can be updated without code changes
Test suite validating each routing rule produces the correct model selection

Error Handling

Error	Cause	Fix
No rule matched	Conditions don't cover all cases	Always include a default catch-all rule at the end
Rule evaluation error	Dynamic rule query failed (e.g., cost API timeout)	Add fallback values for dynamic data; never block on rule evaluation
Wrong model selected	Rule priority order incorrect	Add logging to show which rule matched and why; review priority ordering

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

Examples

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

openrouter-routing-rules

openrouter-routing-rules

Openrouter Routing Rules

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources

Openrouter Routing Rules

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources