Skip to main content
ClaudeWave
Skill6.1k estrellas del repoactualizado today

cli-setup

The cli-setup skill provides OmniRoute command-line interface configuration and initialization through subcommands for managing autostart behavior, tool configurations, and environment variables. Use it to install OmniRoute globally, configure tool-specific settings with model selection, validate configurations, manage environment variables, enable or disable autostart functionality, and perform initial setup with provider authentication options.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/diegosouzapw/OmniRoute /tmp/cli-setup && cp -r /tmp/cli-setup/skills/cli-setup ~/.claude/skills/cli-setup
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

<!-- 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 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`

**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`

**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
```