cli-setup — Claude Code skill: what it does, how to install
Helps the agent configure OmniRoute, manage autostart, apply CLI updates, and adjust session environment variables.
npx skills add cheaper-inference/OmniRoute --skill cli-setup -a claude-codeWhat cli-setup does
The skill teaches the agent how to execute omniroute subcommands. It details flags for provider registration, autostart toggles, and CLI update routines. The machine must have omniroute installed globally or available through npx omniroute.
Command coverage includes setup flags like --add-provider, --api-key, and --default-model. It also documents config validate <tool> to verify tool formatting before writing any changes to disk.
Keep in mind that omniroute env set <key> <value> modifies variables only for the current terminal session. Persistent system variables require a different approach.
What it helps with
- configure model providers with
omniroute setup - enable, disable, or inspect autostart status
- validate tool configuration format before saving changes
- check and apply updates using
omniroute update
Example prompts for the agent
- Run provider setup with omniroute setup --add-provider
- Check autostart status using omniroute autostart status
- Show active environment variables using omniroute env show --json
How to install cli-setup
1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-setup -a claude-code2Manually: put the files in place
~/.claude/skills/cli-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cli-setup/
1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-setup -a codex2Manually: put the files in place
.agents/skills/cli-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-setup -a cursor2Manually: put the files in place
.cursor/skills/cli-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cheaper-inference/OmniRoute cli-setup2Manually: put the files in place
.github/skills/cli-setup/SKILL.md1Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/cheaper-inference/OmniRoute --path skills/cli-setupManually: put the files in place
.devin/skills/cli-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cheaper-inference/OmniRoute --skill cli-setup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set34
The whole set →Similar
Questions about cli-setup
How to install cli-setup in Claude Code?
Run npx skills add cheaper-inference/OmniRoute --skill cli-setup -a claude-code in your terminal.
What does cli-setup do?
It provides command references and flags for omniroute, covering initial setup, autostart control, config validation, and updates.
Do variables from omniroute env set persist across sessions?
No, running omniroute env set <key> <value> assigns variables strictly for the active terminal session.
Source text
SKILL.md · MIT
--- name: cli-setup description: Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI setup and config commands. --- <!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten --> ## Overview Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI setup and config commands. ## Quick install ```bash npm install -g omniroute # or: npx omniroute omniroute --version ``` ## Subcommands ### `autostart` **Example:** ```bash omniroute autostart ``` ### `autostart enable` **Example:** ```bash omniroute autostart enable ``` ### `autostart disable` **Example:** ```bash omniroute autostart disable ``` ### `autostart toggle` **Example:** ```bash omniroute autostart toggle ``` ### `autostart status` **Example:** ```bash omniroute autostart status ``` ### `config` Show or update CLI tool configuration **Example:** ```bash omniroute config ``` ### `config list` List all CLI tools and config status **Flags:** - `--json` **Example:** ```bash omniroute config list ``` ### `config get <tool>` Show current config for a tool **Flags:** - `--json` **Example:** ```bash omniroute config get <tool> ``` ### `config set <tool>` Write config for a tool **Flags:** - `--model <model>` - `--non-interactive` - `--yes` - `--allow-container-write` **Example:** ```bash omniroute config set <tool> ``` ### `config validate <tool>` Validate config format without writing **Flags:** - `--model <model>` - `--json` **Example:** ```bash omniroute config validate <tool> ``` ### `config opencode` Generate OpenCode config (alias for **Flags:** - `--model <model>` - `--non-interactive` - `--yes` - `--allow-container-write` **Example:** ```bash omniroute config opencode ``` ### `config lang` **Example:** ```bash omniroute config lang ``` ### `config get` **Flags:** - `--json` **Example:** ```bash omniroute config get ``` ### `config set <code>` **Flags:** - `--force` **Example:** ```bash omniroute config set <code> ``` ### `config list` **Flags:** - `--json` **Example:** ```bash omniroute config list ``` ### `env` Show and manage environment variables **Example:** ```bash omniroute env ``` ### `env show` Show current environment variables **Flags:** - `--json` **Example:** ```bash omniroute env show ``` ### `env get <key>` Get a single environment variable **Example:** ```bash omniroute env get <key> ``` ### `env set <key> <value>` Set an environment variable (current session only) **Example:** ```bash omniroute env set <key> <value> ``` ### `setup` **Flags:** - `--password <value>` - `--add-provider` - `--provider <id>` - `--provider-name <name>` - `--api-key <value>` - `--default-model <model>` - `--provider-base-url <url>` - `--test-provider` - `--non-interactive` - `--list` **Example:** ```bash omniroute setup ``` ### `update` **Flags:** - `--check` - `--apply` - `--changelog` - `--dry-run` - `--no-backup` - `--yes` **Example:** ```bash omniroute update ```
© cheaper-inference · MIT · cheaper-inference/OmniRoute