openrouter-known-pitfalls
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'.
When & Why to Use This Skill
The OpenRouter Known Pitfalls skill is a specialized developer assistant designed to streamline LLM integration by identifying and preventing common mistakes, anti-patterns, and technical 'gotchas.' It acts as an automated expert during code reviews and developer onboarding, ensuring that OpenRouter implementations are robust, cost-effective, and follow best practices for API connectivity and error handling.
Use Cases
- Automated Code Review: Scanning pull requests to detect OpenRouter-specific anti-patterns and ensuring code quality before merging.
- Developer Onboarding: Providing a structured guide for new engineers to learn the nuances of the OpenRouter API and avoid frequent integration errors.
- Troubleshooting & Debugging: Quickly identifying the root causes of API failures or unexpected model behavior by checking against known pitfalls.
- Best Practice Enforcement: Ensuring consistent implementation of logging, monitoring, and error-handling strategies across all LLM-powered features.
| name | openrouter-known-pitfalls |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
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 {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.