Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
60
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Risky
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./skills/cli-providers/SKILL.mdManage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
npm install -g omniroute # or: npx omniroute
omniroute --versionprovider-cmd provider [subcommand]Manage provider connections (use
Example:
omniroute provider-cmd provider [subcommand]providersExample:
omniroute providersproviders availableShow available providers in the OmniRoute catalog
Flags:
--json--search <query>-q, --q <query>--category <category>Example:
omniroute providers availableproviders listList configured provider connections
Flags:
--jsonExample:
omniroute providers listproviders test <idOrName>Test a configured provider connection
Flags:
--jsonExample:
omniroute providers test <idOrName>providers test-allTest all active provider connections
Flags:
--jsonExample:
omniroute providers test-allproviders validateValidate local provider configuration without calling upstream
Flags:
--jsonExample:
omniroute providers validateproviders rotate <idOrName>Flags:
--new-key <key>--from-env <VAR>--oauth--yes--skip-test--dry-runExample:
omniroute providers rotate <idOrName>providers statusFlags:
--provider <name>--jsonExample:
omniroute providers statusproviders metricsFlags:
--provider <id>--connection-id <id>--period <p>--metric <m>--sort-by <field>--limit <n>--watch--compare <list>Example:
omniroute providers metricsproviders metric <connectionId> <metric>Flags:
--period <p>Example:
omniroute providers metric <connectionId> <metric>test-provider test [provider] [model]Flags:
--all-providers--json--latency--repeat <n>--compare <models>--save <path>Example:
omniroute test-provider test [provider] [model]Requires the omniroute CLI. See CLI entry-point skill for install + global flags.
omniroute providers available # Full OmniRoute provider catalog
omniroute providers available --search openai # Filter by id, name, alias
omniroute providers available --category api-key # Filter by category
omniroute providers available --json # Machine-readable JSONCategories: api-key, oauth, free, local, combo.
omniroute providers list # Connections in your DB
omniroute providers list --jsonomniroute providers test <id|name> # Test one configured connection
omniroute providers test-all # Test every active connection (TUI progress)
omniroute providers validate # Local-only structural validation (no HTTP)test-all opens an interactive TUI that shows live pass/fail per connection. Use --json to get a machine-readable result:
omniroute providers test-all --jsonThese manage the OmniRoute API keys issued under API Manager — not provider credentials.
omniroute keys list # List all OmniRoute API keys
omniroute keys add <provider> [apiKey] # Add an API key for a provider
omniroute keys remove <provider> # Remove an API key
omniroute keys regenerate <id> # Regenerate (rotate) a key
omniroute keys revoke <id> # Revoke a key (disables it)
omniroute keys reveal <id> # Show the full key value
omniroute keys usage <id> # Show usage stats for a key
omniroute keys rotate <id> # Rotate + revoke old key atomically
omniroute keys expiration list # List key expiration timesomniroute keys policy show <id> # Show rate-limit / permission policy
omniroute keys policy set <id> \
--rate-limit 100 \
--rate-window minute \
--permissions chat,models # Set policy on a keyomniroute models # List all models (all providers)
omniroute models openai # Filter by provider
omniroute models --search gpt # Search by name
omniroute models --json # JSON outputomniroute oauth list # List OAuth-configured providers
omniroute oauth login <provider> # Start browser-based OAuth flow
omniroute oauth logout <provider> # Revoke OAuth token
omniroute oauth status <provider> # Show token state + expiry
omniroute oauth refresh <provider> # Force token refreshFor OAuth providers (Gemini, Windsurf, Antigravity, etc.) the login command opens the OmniRoute dashboard OAuth flow in your browser.
Provider nodes let you attach multiple API keys / accounts to one logical provider for round-robin or failover.
omniroute nodes list <provider> # List nodes for a provider
omniroute nodes add <provider> --api-key <key> # Add a node
omniroute nodes remove <provider> <nodeId> # Remove a node
omniroute nodes test <provider> <nodeId> # Test one nodeCreate and manage routing combos from the terminal:
omniroute combo list # List all combos
omniroute combo create <name> \
--strategy priority \
--targets anthropic/claude-opus-4-7,openai/gpt-4o # Create combo
omniroute combo switch <name> # Activate a combo as default
omniroute combo delete <name> # Delete a combo
omniroute combo suggest --task "code review" # Ask OmniRoute to recommend a comboFor the full REST API for combos see omniroute-routing skill.
omniroute quota # Provider quota usage + reset times
omniroute usage # Request + token usage summary
omniroute cost # Cost breakdown (by provider/model)omniroute compression status # Current compression mode + savings stats
omniroute compression set --mode rtk # Enable RTK compression
omniroute compression set --mode stacked # Enable stacked (RTK + Caveman)
omniroute compression set --mode off # Disable compression
omniroute compression preview --mode rtk --text "..." # Preview savings for sample textomniroute health # Detailed health: circuit breakers, cache, memoryproviders test <id> fails with 401 → API key stored for that provider is wrong; use keys remove + keys add to reset itoauth login opens but doesn't complete → the OAuth token endpoint may be firewalled; use API key auth insteadcombo create fails with strategy unknown → use one of: priority, weighted, round-robin, fill-first, least-used, cost-optimized, auto, random, strict-random, p2c, reset-aware, lkgp, context-optimized, context-relay3070925
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.