/cli-providers
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
$ npx -y skills add diegosouzapw/OmniRoute --skill cli-providers --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/cli-providers
Context preview
The summary Claude sees to decide when to auto-load this skill.
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
SKILL.md
cli-providers.SKILL.mdname: cli-providers
description: "Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics."
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
Overview
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
Quick install
npm install -g omniroute # or: npx omniroute
omniroute --version
Subcommands
`provider-cmd provider [subcommand]`
Manage provider connections (use
**Example:**
omniroute provider-cmd provider [subcommand]
`providers`
**Example:**
omniroute providers
`providers available`
Show available providers in the OmniRoute catalog
**Flags:**
- `--json`
- `--search <query>`
- `-q, --q <query>`
- `--category <category>`
**Example:**
omniroute providers available
`providers list`
List configured provider connections
**Flags:**
- `--json`
**Example:**
omniroute providers list
`providers test <idOrName>`
Test a configured provider connection
**Flags:**
- `--json`
**Example:**
omniroute providers test <idOrName>
`providers test-all`
Test all active provider connections
**Flags:**
- `--json`
**Example:**
omniroute providers test-all
`providers validate`
Validate local provider configuration without calling upstream
**Flags:**
- `--json`
**Example:**
omniroute providers validate
`providers rotate <idOrName>`
**Flags:**
- `--new-key <key>`
- `--from-env <VAR>`
- `--oauth`
- `--yes`
- `--skip-test`
- `--dry-run`
**Example:**
omniroute providers rotate <idOrName>
`providers status`
**Flags:**
- `--provider <name>`
- `--json`
**Example:**
omniroute providers status
`providers metrics`
**Flags:**
- `--provider <id>`
- `--connection-id <id>`
- `--period <p>`
- `--metric <m>`
- `--sort-by <field>`
- `--limit <n>`
- `--watch`
- `--compare <list>`
**Example:**
omniroute providers metrics
`providers 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]
<!-- skill:custom-start --> <!-- Migrated from skills/omniroute-cli-providers/SKILL.md (preserved curated content) -->
OmniRoute — CLI Providers & Keys
Requires the `omniroute` CLI. See [CLI entry-point skill](https://raw.githubusercontent.com/diegosouzapw/OmniRoute/main/skills/omniroute-cli/SKILL.md) for install + global flags.
Provider catalog (available providers)
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 JSON
Categories: `api-key`, `oauth`, `free`, `local`, `combo`.
Configured provider connections
omniroute providers list # Connections in your DB
omniroute providers list --json
Testing connections
omniroute 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 --json
API key management (OmniRoute keys)
These 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 times
Key policies
omniroute 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 key
Models
omniroute models # List all models (all providers)
omniroute models openai # Filter by provider
omniroute models --search gpt # Search by name
omniroute models --json # JSON output
OAuth providers
omniroute 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 refresh
For OAuth providers (Gemini, Windsurf, Antigravity, etc.) the `login
Read more
name: cli-providers description: "Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics."
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
Overview
Manage provider connections from the CLI: list available/configured providers, add, test, test-all, validate, rotate API keys, and view per-provider metrics.
Quick install
npm install -g omniroute # or: npx omniroute omniroute --version
Subcommands
`provider-cmd provider [subcommand]`
Manage provider connections (use
**Example:**
omniroute provider-cmd provider [subcommand]
`providers`
**Example:**
omniroute providers
`providers available`
Show available providers in the OmniRoute catalog
**Flags:**
- `--json`
- `--search <query>`
- `-q, --q <query>`
- `--category <category>`
**Example:**
omniroute providers available
`providers list`
List configured provider connections
**Flags:**
- `--json`
**Example:**
omniroute providers list
`providers test <idOrName>`
Test a configured provider connection
**Flags:**
- `--json`
**Example:**
omniroute providers test <idOrName>
`providers test-all`
Test all active provider connections
**Flags:**
- `--json`
**Example:**
omniroute providers test-all
`providers validate`
Validate local provider configuration without calling upstream
**Flags:**
- `--json`
**Example:**
omniroute providers validate
`providers rotate <idOrName>`
**Flags:**
- `--new-key <key>`
- `--from-env <VAR>`
- `--oauth`
- `--yes`
- `--skip-test`
- `--dry-run`
**Example:**
omniroute providers rotate <idOrName>
`providers status`
**Flags:**
- `--provider <name>`
- `--json`
**Example:**
omniroute providers status
`providers metrics`
**Flags:**
- `--provider <id>`
- `--connection-id <id>`
- `--period <p>`
- `--metric <m>`
- `--sort-by <field>`
- `--limit <n>`
- `--watch`
- `--compare <list>`
**Example:**
omniroute providers metrics
`providers 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]
<!-- skill:custom-start --> <!-- Migrated from skills/omniroute-cli-providers/SKILL.md (preserved curated content) -->
OmniRoute — CLI Providers & Keys
Requires the `omniroute` CLI. See [CLI entry-point skill](https://raw.githubusercontent.com/diegosouzapw/OmniRoute/main/skills/omniroute-cli/SKILL.md) for install + global flags.
Provider catalog (available providers)
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 JSON
Categories: `api-key`, `oauth`, `free`, `local`, `combo`.
Configured provider connections
omniroute providers list # Connections in your DB omniroute providers list --json
Testing connections
omniroute 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 --json
API key management (OmniRoute keys)
These 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 times
Key policies
omniroute 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 key
Models
omniroute models # List all models (all providers) omniroute models openai # Filter by provider omniroute models --search gpt # Search by name omniroute models --json # JSON output
OAuth providers
omniroute 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 refresh
For OAuth providers (Gemini, Windsurf, Antigravity, etc.) the `login
Never stop coding. Free MIT AI gateway: one endpoint, 290+ providers (90+ free), 500+ models — Kimi, Claude, GPT, OpenAI, Gemini, GLM, DeepSeek, MiniMax. Works with Claude Code, Codex, Cursor, OpenCode, Cline & Copilot. Quota-aware auto-fallback, RTK+Caveman compression saves 15-95% tokens, MCP/A2A, Desktop/PWA. Built by 500+ contributors
Repo: diegosouzapw/OmniRoute
Other skills on omniroute.
- /cli-a2a
Interact with the OmniRoute A2A server from the CLI. Send tasks, inspect skill execution history, and test the JSON-RPC 2.0 agent-to-agent protocol interactively.
Open skill - /cli-backup-sync
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
Open skill - /cli-batches
Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD workflows.
Open skill - /cli-chat
Send chat completions, stream responses, and start an interactive REPL session from the CLI. Supports all OmniRoute providers, combo routing, and system prompt configuration.
Open skill - /cli-compression
Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview compression output with real prompts.
Open skill - /cli-contexts
Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI. Apply context-relay settings and inspect active context pipelines.
Open skill

