name: openrouter-known-pitfalls description: Execute avoid common OpenRouter mistakes and anti-patterns. Use when reviewing code or onboarding developers. Trigger with phrases like 'openrouter pitfalls', 'openrouter mistakes', 'openrouter gotchas', 'openrouter common issues'. license: MIT
Openrouter Known Pitfalls
Overview
This skill documents common mistakes, anti-patterns, and gotchas to avoid when working with OpenRouter.
Prerequisites
- OpenRouter integration or planning one
Instructions
Follow these steps to implement this skill:
- Verify Prerequisites: Ensure all prerequisites listed above are met
- Review the Implementation: Study the code examples and patterns below
- Adapt to Your Environment: Modify configuration values for your setup
- Test the Integration: Run the verification steps to confirm functionality
- Monitor in Production: Set up appropriate logging and monitoring
Output
Successful execution produces:
- Working OpenRouter integration
- Verified API connectivity
- Example responses demonstrating functionality
Error Handling
See references/errors.md for comprehensive error handling.
Examples
See references/examples.md for detailed examples.
Reference Guides
- Authentication Issues — Wrong key formats, missing Bearer prefix, hardcoded keys
- Cost Surprises — Missing max_tokens, wrong model for task, no cost tracking
- Error Handling Gaps — Missing error handling, empty response handling
- Model Name Mistakes — Missing provider prefix, typos, deprecated names
- Provider Differences — Assuming identical behavior, different response formats
- Rate Limiting Mistakes — No backoff strategy, ignoring rate limit headers
- Request Format Errors — Invalid message structure, alternating roles violation