Skill

openrouter-known-pitfalls

Avoid common OpenRouter integration pitfalls and gotchas. Use proactively when designing or reviewing an integration. Trigger with phrases like 'openrouter pitfalls', 'openrouter gotchas', 'openrouter mistakes', 'openrouter best practices'.

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/authentication-issues.md

references/cost-surprises.md

references/error-handling-gaps.md

references/errors.md

references/examples.md

references/model-name-mistakes.md

references/provider-differences.md

references/rate-limiting-mistakes.md

references/request-format-errors.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

Avoid hardcoding model IDs: Models get renamed or removed; always validate model availability at startup and handle missing models gracefully

Don't ignore token limits: Each model has different context windows; always check context_length from the models API and validate prompt size before sending

Handle provider differences: The same prompt can produce different results across providers; test critical prompts with your specific model, not just any model

Set max_tokens explicitly: Without max_tokens, models may generate very long (and expensive) responses; always set a reasonable limit

Don't store API keys in code: Use environment variables or a secrets manager; add .env to .gitignore; rotate keys if they're ever exposed

Error Handling

Error

Cause

Fix

model_not_found after working fine

Model was renamed or deprecated

Query /models at startup; maintain a fallback model list

Unexpectedly large bill

No max_tokens set on expensive model

Always set max_tokens; implement cost tracking middleware

Different behavior across models

Assuming all models handle prompts identically

Test with each model you plan to use; adjust prompts per model if needed

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

Openrouter Known Pitfalls

Overview

This skill documents the most common mistakes developers make when integrating OpenRouter and how to avoid them.

Prerequisites

OpenRouter integration (planned or existing)

Instructions

Avoid hardcoding model IDs: Models get renamed or removed; always validate model availability at startup and handle missing models gracefully
Don't ignore token limits: Each model has different context windows; always check context_length from the models API and validate prompt size before sending
Handle provider differences: The same prompt can produce different results across providers; test critical prompts with your specific model, not just any model
Set max_tokens explicitly: Without max_tokens, models may generate very long (and expensive) responses; always set a reasonable limit
Don't store API keys in code: Use environment variables or a secrets manager; add .env to .gitignore; rotate keys if they're ever exposed

Output

Checklist of common pitfalls with prevention strategies
Code review checklist for OpenRouter integrations
Configuration validation script that catches common mistakes

Error Handling

Error	Cause	Fix
`model_not_found` after working fine	Model was renamed or deprecated	Query `/models` at startup; maintain a fallback model list
Unexpectedly large bill	No `max_tokens` set on expensive model	Always set `max_tokens`; implement cost tracking middleware
Different behavior across models	Assuming all models handle prompts identically	Test with each model you plan to use; adjust prompts per model if needed

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

Examples

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

openrouter-known-pitfalls

openrouter-known-pitfalls

Openrouter Known Pitfalls

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources

Openrouter Known Pitfalls

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources