Cli Setup
Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI setup and config commands.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Cli Setup when an AI agent needs a reusable SKILL.md workflow for this job: Run initial setup, configure global CLI settings, manage environment variables, check for updates, and configure autostart via the CLI setup and config commands.
When not to use it
Skip Cli Setup 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-setup # Save SKILL.md to ~/.claude/skills/cli-setup/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-setup/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-setup/ 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 Setup skill for this task: Use Cli Setup 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.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- 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
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`
**Flags:**
- `--tray` - `--no-tray`
**Example:**
```bash omniroute autostart enable ```
### `autostart disable`
**Example:**
```bash omniroute autostart disable ```
### `autostart toggle`
**Flags:**
- `--tray` - `--no-tray`
**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 ```
Intended uses
- Use Cli Setup 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.