Cli Resilience
Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Cli Resilience when an AI agent needs a reusable SKILL.md workflow for this job: Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.
When not to use it
Skip Cli Resilience 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-resilience # Save SKILL.md to ~/.claude/skills/cli-resilience/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-resilience/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-resilience/ 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 Resilience skill for this task: Use Cli Resilience 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
Inspect and manage circuit-breaker states, connection cooldowns, quota limits, and backoff levels from the CLI. Reset stuck providers and configure resilience thresholds.
## Quick install
```bash npm install -g omniroute # or: npx omniroute omniroute --version ```
## Subcommands
### `quota`
**Flags:**
- `--provider <id>` - `--json`
**Example:**
```bash omniroute quota ```
### `quota status`
Show truthful OmniRoute gateway, quota, pool, and circuit state
**Example:**
```bash omniroute quota status ```
### `quota preview`
Preview allocation enforcement without an upstream request
**Flags:**
- `--api-key-id <id>` - `--pool-id <id>` - `--tokens <n>`
**Example:**
```bash omniroute quota preview ```
### `quota ensure <json>`
Idempotently create or update a quota pool from a JSON object
**Example:**
```bash omniroute quota ensure <json> ```
### `resilience`
**Example:**
```bash omniroute resilience ```
### `resilience status`
**Flags:**
- `--provider <p>`
**Example:**
```bash omniroute resilience status ```
### `resilience breakers`
**Flags:**
- `--provider <p>`
**Example:**
```bash omniroute resilience breakers ```
### `resilience cooldowns`
**Flags:**
- `--provider <p>` - `--connection-id <id>`
**Example:**
```bash omniroute resilience cooldowns ```
### `resilience lockouts`
**Flags:**
- `--provider <p>` - `--model <m>`
**Example:**
```bash omniroute resilience lockouts ```
### `resilience reset`
**Flags:**
- `--provider <p>` - `--connection-id <id>` - `--model <m>` - `--all-cooldowns` - `--yes`
**Example:**
```bash omniroute resilience reset ```
### `resilience profile`
**Example:**
```bash omniroute resilience profile ```
### `resilience show`
**Example:**
```bash omniroute resilience show ```
### `resilience set <name>`
**Example:**
```bash omniroute resilience set <name> ```
### `resilience config`
**Example:**
```bash omniroute resilience config ```
### `resilience show`
**Example:**
```bash omniroute resilience show ```
### `resilience set`
**Flags:**
- `--threshold <n>` - `--reset-timeout <ms>` - `--base-cooldown <ms>`
**Example:**
```bash omniroute resilience set ```
Intended uses
- Use Cli Resilience 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.