Configuration validation and testing utilities for OpenRouter API. Use when validating API keys, testing model availability, checking routing configuration, troubleshooting connection issues, analyzing usage costs, or when user mentions OpenRouter validation, config testing, API troubleshooting, model availability, or cost analysis.
View on GitHubFebruary 1, 2026
Select agents to install to:
npx add-skill https://github.com/vanman2024/ai-dev-marketplace/blob/main/plugins/openrouter/skills/openrouter-config-validator/SKILL.md -a claude-code --skill openrouter-config-validatorInstallation paths:
.claude/skills/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 1. **API Key Validation**: Format checking and connectivity testing 2. **Model Availability Checking**: Verify requested models are accessible 3. **Routing Configuration Testing**: Validate model routing and fallback chains 4. **Environment Validation**: Check .env file completeness and correctness 5. **Fallback Testing**: Test fallback chain execution and behavior 6. **Provider Status Checking**: Monitor provider availability and health 7. **Usage Analysis**: Track API usage patterns and cost optimization 8. **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 bash scripts/validate-api-key.sh <api-key> ``` **Model Availability Check:** ```bash bash scripts/check-model-availability.sh <model-id> ``` **Routing Configuration Test:** ```bash bash scripts/test-routing.sh <config-file> ``` **Environment Validation:** ```bash bash scripts/validate-env-config.sh <env-file> ``` **Fallback Chain Testing:** ```bash bash scripts/test-fallback.sh <fallback-config> ``` **Provider Status Check:** ```bash bash scripts/check-provider-status.sh <provider-name> ``` **Usage Analysis:** ```bash bash scripts/analyze-usage.sh <date-range> ``` **Comprehensive Troubleshooting:** ```bash bash scripts/troubleshoot.sh ``` ### Phase 3: Load Appropriate Template Use templates from `templates/` directory