openrouter-config-validator
OpenRouter Config Validator
Comprehensive validation and testing utilities for OpenRouter API configuration, model availability, routing setup, and cost monitoring.
What This Skill Provides
- API Key Validation: Format checking and connectivity testing
- Model Availability Checking: Verify requested models are accessible
- Routing Configuration Testing: Validate model routing and fallback chains
- Environment Validation: Check .env file completeness and correctness
- Fallback Testing: Test fallback chain execution and behavior
- Provider Status Checking: Monitor provider availability and health
- Usage Analysis: Track API usage patterns and cost optimization
- Troubleshooting: Comprehensive diagnostic tools for common issues
Instructions
Phase 1: Identify Validation Need
Determine what needs validation:
- API key format and connectivity
- Model availability and access
- Routing configuration correctness
- Environment variable completeness
- Fallback chain behavior
- Provider health status
- Usage patterns and costs
- General troubleshooting
Phase 2: Run Appropriate Validation Script
Execute the relevant validation script from scripts/ directory:
API Key Validation:
bash scripts/validate-api-key.sh <api-key>
Model Availability Check:
bash scripts/check-model-availability.sh <model-id>
Routing Configuration Test:
bash scripts/test-routing.sh <config-file>
Environment Validation:
bash scripts/validate-env-config.sh <env-file>
Fallback Chain Testing:
bash scripts/test-fallback.sh <fallback-config>
Provider Status Check:
bash scripts/check-provider-status.sh <provider-name>
Usage Analysis:
bash scripts/analyze-usage.sh <date-range>
Comprehensive Troubleshooting:
bash scripts/troubleshoot.sh
Phase 3: Load Appropriate Template
Use templates from templates/ directory for configuration:
Environment Setup:
templates/.env.template- Complete configuration templatetemplates/.env.example- Minimal configuration example
Monitoring Configuration:
templates/monitoring-config.json- X-Title and HTTP-Referer setuptemplates/budget-alerts.json- Cost alert configuration
Provider Preferences:
templates/provider-preferences.json- Provider routing preferences
Phase 4: Reference Troubleshooting Examples
Check examples/ directory for common issue resolutions:
examples/api-key-troubleshooting.md- API key issuesexamples/model-not-found.md- Model availability problemsexamples/rate-limiting.md- Rate limit handlingexamples/fallback-issues.md- Fallback chain debuggingexamples/cost-optimization.md- Cost reduction strategiesexamples/provider-errors.md- Provider-specific errors
Phase 5: Report Results
Summarize validation results:
- What was tested
- Issues found (if any)
- Recommended fixes
- Next steps
When Agents Should Use This Skill
Automatic triggers:
- Setting up new OpenRouter integration
- Debugging API connection failures
- Validating configuration before deployment
- Troubleshooting model access issues
- Analyzing unexpected API costs
- Testing fallback chain behavior
- Monitoring provider health
User-requested scenarios:
- "Validate my OpenRouter configuration"
- "Test if model X is available"
- "Why is my fallback chain not working?"
- "Check my API usage costs"
- "Troubleshoot OpenRouter connection"
- "Verify my routing configuration"
Validation Capabilities
API Key Validation
- Format checking (sk-or-v1-* pattern)
- Connectivity testing via /auth/key endpoint
- Permission verification
- Credit balance checking
Model Availability
- Model ID existence verification
- Provider availability checking
- Access permission validation
- Alternative model suggestions
Configuration Testing
- .env file completeness
- Required variable presence
- Format validation
- Value sanity checks
Routing Validation
- Model routing configuration
- Fallback chain structure
- Provider preference validation
- Cost optimization checks
Usage Analysis
- Request volume tracking
- Cost breakdowns by model
- Provider distribution
- Rate limit monitoring
- Budget alert configuration
Script Reference
All scripts located in skills/openrouter-config-validator/scripts/:
validate-api-key.sh- API key format and connectivitycheck-model-availability.sh- Model access verificationtest-routing.sh- Routing configuration testingvalidate-env-config.sh- Environment validationtest-fallback.sh- Fallback chain testingcheck-provider-status.sh- Provider health monitoringanalyze-usage.sh- Usage pattern analysistroubleshoot.sh- Comprehensive diagnostics
Template Reference
All templates located in skills/openrouter-config-validator/templates/:
.env.template- Complete environment configuration.env.example- Minimal configuration examplemonitoring-config.json- Request monitoring setupbudget-alerts.json- Cost alert configurationprovider-preferences.json- Provider routing preferences
Example Reference
All examples located in skills/openrouter-config-validator/examples/:
api-key-troubleshooting.md- Common API key issuesmodel-not-found.md- Model availability solutionsrate-limiting.md- Rate limit handling strategiesfallback-issues.md- Fallback debugging guidecost-optimization.md- Cost reduction techniquesprovider-errors.md- Provider-specific error handling
Requirements
- bash 4.0+
- curl (for API testing)
- jq (for JSON parsing)
- OpenRouter API key (for live testing)
- Internet connectivity (for API calls)
Skill Location: plugins/openrouter/skills/openrouter-config-validator/ Version: 1.0.0