Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview compression output with real prompts.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add diegosouzapw/OmniRoute --skill cli-compression --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cli Compression?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/diegosouzapw-cli-compression)More formats (shields.io, HTML) on the badges page.
---
name: cli-compression
description: Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview compression output with real prompts.
---
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
## Overview
Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview compression output with real prompts.
## Quick install
```bash
npm install -g omniroute # or: npx omniroute
omniroute --version
```
## Subcommands
### `compression`
**Example:**
```bash
omniroute compression
```
### `compression status`
**Example:**
```bash
omniroute compression status
```
### `compression configure`
**Flags:**
- `--engine <e>`
- `--caveman-aggressiveness <n>`
- `--rtk-budget <n>`
- `--language-pack <p>`
**Example:**
```bash
omniroute compression configure
```
### `compression engine`
**Example:**
```bash
omniroute compression engine
```
### `compression set <name>`
**Example:**
```bash
omniroute compression set <name>
```
### `compression get`
**Example:**
```bash
omniroute compression get
```
### `compression combos`
**Example:**
```bash
omniroute compression combos
```
### `compression list`
**Example:**
```bash
omniroute compression list
```
### `compression stats`
**Flags:**
- `--period <p>`
**Example:**
```bash
omniroute compression stats
```
### `compression rules`
**Example:**
```bash
omniroute compression rules
```
### `compression list`
**Example:**
```bash
omniroute compression list
```
### `compression add`
**Flags:**
- `--replacement <r>`
**Example:**
```bash
omniroute compression add
```
### `compression remove <id>`
**Flags:**
- `--yes`
**Example:**
```bash
omniroute compression remove <id>
```
### `compression language-packs`
**Example:**
```bash
omniroute compression language-packs
```
### `compression preview`
**Example:**
```bash
omniroute compression preview
```
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.