Skip to main content
Agent skill

Cli Skill Collector

Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.

Get started

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

When to use this skill

Use Cli Skill Collector when an AI agent needs a reusable SKILL.md workflow for this job: Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.

When not to use it

Skip Cli Skill Collector 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-skill-collector
# Save SKILL.md to ~/.claude/skills/cli-skill-collector/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-skill-collector/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-skill-collector/ 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 Skill Collector skill for this task: Use Cli Skill Collector when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/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
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiinferred

    The skill text mentions Gemini or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • copilotinferred

    The skill text mentions Copilot or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • 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

Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.

## Quick install

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

## Subcommands

### `autostart`

**Example:**

```bash omniroute autostart ```

### `autostart enable`

**Flags:**

- `--tray` - `--no-tray`

**Example:**

```bash omniroute autostart enable ```

### `autostart disable`

**Example:**

```bash omniroute autostart disable ```

### `autostart toggle`

**Flags:**

- `--tray` - `--no-tray`

**Example:**

```bash omniroute autostart toggle ```

### `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` - `--allow-container-write`

**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` - `--allow-container-write`

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

<!-- skill:custom-start --> <!-- Preserved curated content from #6294 (skills/cli-skill-collector authored workflow) -->

# /cli-skill-collector — Agent Skill Collector

Discover and install agent skills for your coding CLI tools — all through OmniRoute's built-in APIs.

This skill teaches you how to:

1. **Detect** which coding CLIs are installed on this machine 2. **Search** GitHub for relevant agent skills (SKILL.md repos) 3. **Install** discovered skills to the detected coding tools

No separate Skill Collector app needed — OmniRoute's own CLI detection + GitHub search handles everything.

---

## Step 1 — Detect installed coding tools

Query OmniRoute's CLI tool detection to find which coding agents are installed:

```bash curl -H "Authorization: Bearer $OMNIROUTE_API_KEY" http://localhost:20128/api/skills/collect/detect ```

This returns:

- Every CLI tool in OmniRoute's catalog (`CLI_TOOL_IDS`: claude, codex, cursor, copilot, opencode, cline, kilocode, hermes, hermes-agent, openclaw, droid, continue, qwen, windsurf, devin, antigravity, etc.) - Whether each is **installed** and **runnable** - GitHub skills **matched** to your installed tools (scored by relevance)

Example response:

```json { "tools": { "codex": { "installed": true, "runnable": true, "command": "codex" }, "claude": { "installed": true, "runnable": true, "command": "claude" }, "cursor": { "installed": false, "runnable": false } }, "installedToolIds": ["codex", "claude"], "matchedSkills": [ { "toolId": "codex", "repo": "user/skill-codex-xxx", "score": 0.85, "stars": 120 }, { "toolId": "claude", "repo": "user/claude-agent-rules", "score": 0.92, "stars": 340 } ], "totalSkills": 85 } ```

---

## Step 2 — Review matched skills

For each installed tool, the API returns relevant GitHub repos that contain SKILL.md or agent configuration files. Use the `score` field to prioritize:

| Score | Recommendation | | ----- | ----------------------------------------------- | | 0.80+ | Excellent — well-maintained, high stars, active | | 0.60+ | Good — relevant with decent quality | | 0.40+ | Fair — may need review | | <0.40 | Low quality — skip |

You can also browse manually:

```bash curl -H "Authorization: Bearer $OMNIROUTE_API_KEY" \ "http://localhost:20128/api/github-skills?minStars=3&maxResults=50" ```

---

## Step 3 — Install skills to detected tools

Install a chosen skill to one or more detected tools:

```bash curl -X POST http://localhost:20128/api/skills/collect/install \ -H "Authorization: Bearer $OMNIROUTE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "repoName": "user/skill-codex-xxx", "targets": ["codex", "claude"], "description": "Agent skill for coding workflows" }' ```

This plans the installation path for each target tool:

- **claude** → `~/.claude/skills/{category}/` - **codex** → `~/.codex/skills/{category}/` - **hermes** → `~/AppData/Local/hermes/skills/{category}/` - **opencode** → `~/.opencode/skills/{category}/` - **gemini** → `~/.gemini/skills/{category}/`

The actual file sync (cloning from GitHub and copying SKILL.md) is done by the agent using standard `curl` + `cp` commands.

---

## Step 4 — Verify installation

After installing, verify the skill is in place:

```bash # For Codex ls -la ~/.codex/skills/imported-github/*/SKILL.md

# For Claude Code ls -la ~/.claude/skills/imported-github/*/SKILL.md

# For Hermes (Windows) ls -la ~/AppData/Local/hermes/skills/imported-github/*/SKILL.md ```

Also re-check detection:

```bash curl -H "Authorization: Bearer $OMNIROUTE_API_KEY" http://localhost:20128/api/skills/collect/detect ```

---

## Quick start (full workflow)

```bash AUTH_HEADER="Authorization: Bearer $OMNIROUTE_API_KEY"

# 1. Detect DETECT=$(curl -s -H "$AUTH_HEADER" http://localhost:20128/api/skills/collect/detect)

# 2. Pick top matched skill for first installed tool TOOL=$(echo "$DETECT" | python3 -c "import sys,json;d=json.load(sys.stdin);print(d['installedToolIds'][0] if d['installedToolIds'] else '')") SKILL=$(echo "$DETECT" | python3 -c "import sys,json;d=json.load(sys.stdin);ms=d.get('matchedSkills',[]);print(ms[0]['repo'] if ms else '')")

if [ -n "$TOOL" ] && [ -n "$SKILL" ]; then # 3. Install curl -s -X POST http://localhost:20128/api/skills/collect/install \ -H "$AUTH_HEADER" \ -H "Content-Type: application/json" \ -d "{\"repoName\": \"$SKILL\", \"targets\": [\"$TOOL\"]}" echo "Installed $SKILL to $TOOL" fi ```

---

## Notes

- OmniRoute must be running locally on port 20128 (default) — see `docs/frameworks/SKILLS.md` for custom-port setups. - The `/api/skills/collect/*` and `/api/github-skills` endpoints require **management-scoped authentication** the same way every other `/api/skills/*` route does: a dashboard session, the loopback CLI token, or an API key with the `manage` scope (`requireManagementAuth()`). Auth is only bypassed when the server has no login/API-key requirement configured at all. - This replaces the standalone Skill Collector Python app — all logic is now inside OmniRoute. <!-- skill:custom-end -->

Intended uses

  • Use Cli Skill Collector 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.