Skip to main content
Agent skill

Cli Plugins Skills

Manage Omni Skills (list, install, test, remove), plugins (create, configure), and persistent memory (search, add, clear) from the CLI.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Cli Plugins Skills when an AI agent needs a reusable SKILL.md workflow for this job: Manage Omni Skills (list, install, test, remove), plugins (create, configure), and persistent memory (search, add, clear) from the CLI.

When not to use it

Skip Cli Plugins Skills 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?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/cli-plugins-skills
# Save SKILL.md to ~/.claude/skills/cli-plugins-skills/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-plugins-skills/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-plugins-skills/ instead.
  2. 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.
  3. 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.

Starter prompt
Use the Cli Plugins Skills skill for this task: Use Cli Plugins Skills 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
74/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/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 Omni Skills (list, install, test, remove), plugins (create, configure), and persistent memory (search, add, clear) from the CLI.

## Quick install

```bash npm install -g omniroute # or: npx omniroute omniroute --version ```

## Subcommands

### `memory`

**Example:**

```bash omniroute memory ```

### `memory search <query>`

**Flags:**

- `--type <type>` - `--limit <n>` - `--api-key <key>` - `--token-budget <n>`

**Example:**

```bash omniroute memory search <query> ```

### `memory add`

**Flags:**

- `--content <text>` - `--file <path>` - `--type <type>` - `--metadata <json>` - `--api-key <key>`

**Example:**

```bash omniroute memory add ```

### `memory clear`

**Flags:**

- `--type <type>` - `--older-than <duration>` - `--api-key <key>` - `--yes`

**Example:**

```bash omniroute memory clear ```

### `memory list`

**Flags:**

- `--type <type>` - `--limit <n>` - `--api-key <key>`

**Example:**

```bash omniroute memory list ```

### `memory get <id>`

**Example:**

```bash omniroute memory get <id> ```

### `memory delete <id>`

**Flags:**

- `--yes`

**Example:**

```bash omniroute memory delete <id> ```

### `memory health`

**Example:**

```bash omniroute memory health ```

### `PLUGIN_NAME`

**Example:**

```bash omniroute PLUGIN_NAME ```

### `plugin plugin`

**Example:**

```bash omniroute plugin plugin ```

### `plugin list`

**Example:**

```bash omniroute plugin list ```

### `plugin install <name>`

**Flags:**

- `-y, --yes`

**Example:**

```bash omniroute plugin install <name> ```

### `plugin remove <name>`

**Flags:**

- `-y, --yes`

**Example:**

```bash omniroute plugin remove <name> ```

### `plugin info <name>`

**Example:**

```bash omniroute plugin info <name> ```

### `plugin search [query]`

**Example:**

```bash omniroute plugin search [query] ```

### `plugin update [name]`

**Example:**

```bash omniroute plugin update [name] ```

### `plugin scaffold <name>`

**Example:**

```bash omniroute plugin scaffold <name> ```

### `marketplace`

**Example:**

```bash omniroute marketplace ```

### `skills search [query]`

**Flags:**

- `--category <c>` - `--tag <t>` - `--limit <n>` - `--sort <s>`

**Example:**

```bash omniroute skills search [query] ```

### `skills info <packageId>`

**Example:**

```bash omniroute skills info <packageId> ```

### `skills install <packageId>`

**Flags:**

- `--version <v>` - `--enable` - `--yes`

**Example:**

```bash omniroute skills install <packageId> ```

### `skills categories`

**Example:**

```bash omniroute skills categories ```

### `skills featured`

**Example:**

```bash omniroute skills featured ```

### `skills skills`

**Example:**

```bash omniroute skills skills ```

### `skills list`

**Flags:**

- `--type <type>` - `--enabled` - `--disabled` - `--api-key <key>`

**Example:**

```bash omniroute skills list ```

### `skills get <id>`

**Example:**

```bash omniroute skills get <id> ```

### `skills install`

**Flags:**

- `--from-file <path>` - `--from-url <url>` - `--type <type>` - `--enable`

**Example:**

```bash omniroute skills install ```

### `skills enable <id>`

**Example:**

```bash omniroute skills enable <id> ```

### `skills disable <id>`

**Flags:**

- `--yes`

**Example:**

```bash omniroute skills disable <id> ```

### `skills delete <id>`

**Flags:**

- `--yes`

**Example:**

```bash omniroute skills delete <id> ```

### `skills execute <id>`

**Flags:**

- `--input <json>` - `--input-file <path>` - `--timeout <ms>`

**Example:**

```bash omniroute skills execute <id> ```

### `skills executions`

**Flags:**

- `--skill <id>` - `--limit <n>` - `--status <s>`

**Example:**

```bash omniroute skills executions ```

### `skills skillssh`

**Example:**

```bash omniroute skills skillssh ```

### `skills list`

**Example:**

```bash omniroute skills list ```

### `skills install <url>`

**Example:**

```bash omniroute skills install <url> ```

Intended uses

  • Use Cli Plugins Skills 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.