Cli Models
Query available AI models, list model aliases, and browse the full model catalog from the CLI. Filter by provider, search by capability, and resolve model name variants.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Cli Models when an AI agent needs a reusable SKILL.md workflow for this job: Query available AI models, list model aliases, and browse the full model catalog from the CLI. Filter by provider, search by capability, and resolve model name variants.
When not to use it
Skip Cli Models when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/cli-models # Save SKILL.md to ~/.claude/skills/cli-models/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-models/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-models/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Cli Models skill for this task: Use Cli Models when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptinferred
The skill text mentions ChatGPT or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
## Overview
Query available AI models, list model aliases, and browse the full model catalog from the CLI. Filter by provider, search by capability, and resolve model name variants.
## Quick install
```bash npm install -g omniroute # or: npx omniroute omniroute --version ```
## Subcommands
### `models test-add <model>`
Validate an OpenAI-compatible model on one strict connection, then add it after a synthetic tool round-trip
**Flags:**
- `--provider <id>` - `--connection <id>` - `--name <name>` - `--max-input-tokens <count>` - `--max-output-tokens <count>` - `--api-format <format>` - `--context <name>` - `--base-url <url>` - `--allow-inference` - `--yes` - `--dry-run` - `--json`
**Example:**
```bash omniroute models test-add example-model --provider example-provider --connection example-connection --dry-run ```
### `models [provider]`
**Flags:**
- `--search <query>` - `--json`
**Example:**
```bash omniroute models [provider] ```
### `models manual <provider>`
List manual model metadata from the selected server
**Example:**
```bash omniroute models manual <provider> ```
### `models add <provider> <model-id>`
Add an unverified manual model, then verify persistence
**Flags:**
- `--name <name>` - `--api-format <format>` - `--context-window <tokens>` - `--max-output-tokens <tokens>` - `--dry-run`
**Example:**
```bash omniroute models add <provider> <model-id> ```
### `models edit <provider> <model-id>`
Edit manual model metadata, then verify persistence
**Flags:**
- `--name <name>` - `--api-format <format>` - `--context-window <tokens>` - `--clear-context-window` - `--dry-run`
**Example:**
```bash omniroute models edit <provider> <model-id> ```
### `models remove <provider> <model-id>`
Remove only a manual model override, then verify persistence
**Flags:**
- `--yes` - `--dry-run`
**Example:**
```bash omniroute models remove <provider> <model-id> ```
Intended uses
- Use Cli Models when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.