Cli Contexts
Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI. Apply context-relay settings and inspect active context pipelines.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Cli Contexts when an AI agent needs a reusable SKILL.md workflow for this job: Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI. Apply context-relay settings and inspect active context pipelines.
When not to use it
Skip Cli Contexts 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-contexts # Save SKILL.md to ~/.claude/skills/cli-contexts/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-contexts/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-contexts/ 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 Contexts skill for this task: Use Cli Contexts 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
Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI. Apply context-relay settings and inspect active context pipelines.
## Quick install
```bash npm install -g omniroute # or: npx omniroute omniroute --version ```
## Subcommands
### `context-eng`
**Example:**
```bash omniroute context-eng ```
### `context-eng analytics`
**Flags:**
- `--period <p>`
**Example:**
```bash omniroute context-eng analytics ```
### `context-eng caveman`
**Example:**
```bash omniroute context-eng caveman ```
### `context-eng config`
**Example:**
```bash omniroute context-eng config ```
### `context-eng show`
**Example:**
```bash omniroute context-eng show ```
### `context-eng set`
**Flags:**
- `--aggressiveness <n>` - `--max-shrink-pct <n>` - `--preserve-tags <list>`
**Example:**
```bash omniroute context-eng set ```
### `context-eng rtk`
**Example:**
```bash omniroute context-eng rtk ```
### `context-eng config`
**Example:**
```bash omniroute context-eng config ```
### `context-eng show`
**Example:**
```bash omniroute context-eng show ```
### `context-eng set`
**Flags:**
- `--token-budget <n>` - `--reserve-pct <n>`
**Example:**
```bash omniroute context-eng set ```
### `context-eng filters`
**Example:**
```bash omniroute context-eng filters ```
### `context-eng list`
**Example:**
```bash omniroute context-eng list ```
### `context-eng add`
**Flags:**
- `--pattern <p>` - `--priority <n>` - `--action <a>`
**Example:**
```bash omniroute context-eng add ```
### `context-eng remove <id>`
**Flags:**
- `--yes`
**Example:**
```bash omniroute context-eng remove <id> ```
### `context-eng test`
**Flags:**
- `--file <path>`
**Example:**
```bash omniroute context-eng test ```
### `context-eng raw-output <id>`
**Example:**
```bash omniroute context-eng raw-output <id> ```
### `context-eng combos`
**Example:**
```bash omniroute context-eng combos ```
### `context-eng list`
**Example:**
```bash omniroute context-eng list ```
### `context-eng get <id>`
**Example:**
```bash omniroute context-eng get <id> ```
### `context-eng assignments <id>`
**Example:**
```bash omniroute context-eng assignments <id> ```
### `contexts`
**Example:**
```bash omniroute contexts ```
### `contexts list`
List all contexts
**Example:**
```bash omniroute contexts list ```
### `contexts add <name>`
Add a new context
**Flags:**
- `--url <u>` - `--api-key <k>` - `--api-key-stdin` - `--access-token <t>` - `--access-token-stdin` - `--scope <s>` - `--description <d>`
**Example:**
```bash omniroute contexts add <name> ```
### `contexts use <name>`
Switch active context
**Example:**
```bash omniroute contexts use <name> ```
### `contexts current`
Show the active context (server, auth, scope)
**Flags:**
- `--name-only`
**Example:**
```bash omniroute contexts current ```
### `contexts show <name>`
Show context details
**Example:**
```bash omniroute contexts show <name> ```
### `contexts remove <name>`
Remove a context
**Flags:**
- `--yes`
**Example:**
```bash omniroute contexts remove <name> ```
### `contexts rename <old> <new>`
Rename a context
**Example:**
```bash omniroute contexts rename <old> <new> ```
### `contexts export`
Export contexts to JSON
**Flags:**
- `--out <path>` - `--no-secrets` - `--include-secrets`
**Example:**
```bash omniroute contexts export ```
### `contexts import <file>`
Import contexts from a JSON file
**Flags:**
- `--merge`
**Example:**
```bash omniroute contexts import <file> ```
### `contexts migrate`
Move legacy plaintext context credentials to the OS keychain
**Flags:**
- `--yes`
**Example:**
```bash omniroute contexts migrate ```
### `sessions`
**Example:**
```bash omniroute sessions ```
### `sessions list`
**Flags:**
- `--user <u>` - `--kind <k>` - `--active` - `--limit <n>`
**Example:**
```bash omniroute sessions list ```
### `sessions show <sessionId>`
**Example:**
```bash omniroute sessions show <sessionId> ```
### `sessions expire <sessionId>`
**Flags:**
- `--yes`
**Example:**
```bash omniroute sessions expire <sessionId> ```
### `sessions expire-all`
**Flags:**
- `--user <u>` - `--yes`
**Example:**
```bash omniroute sessions expire-all ```
### `sessions current`
**Example:**
```bash omniroute sessions current ```
Intended uses
- Use Cli Contexts 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.