Skill Router Pro

Skill router and discovery assistant. Use when: - User says "I want to do XXX, what skill do I have" or "is there a skill for XXX" - User doesn't know which...

Security Scan

The skill's requests and instructions are consistent with a skill-discovery/indexing tool, but it omits an explicit dependency on the external 'clawhub' command and instructs reading and writing user skill directories — review file-write behavior and ensure the clawhub binary exists and is trusted before use.

Purpose & Capability

The skill claims to find local skills and search ClawHub; its instructions to read an INDEX.md, search local SKILL.md files, and run 'clawhub search' align with that purpose. However, it references the external 'clawhub' CLI but the skill metadata does not declare that binary as required — a small incoherence (the skill will fail or behave differently if 'clawhub' is absent).

Instruction Scope

SKILL.md explicitly instructs the agent to read and parse files under multiple user directories (~/.openclaw/skills, ~/.mind_claw, ~/.codex/skills, ~/.cursor/skills-cursor) and to write/update ~/.openclaw/skills/INDEX.md. Those actions are within the stated discovery/indexing scope but do involve reading user files and modifying an index file — the user should expect that and may want backups/consent.

Install Mechanism

Instruction-only skill with no install spec or code to download; low install risk. No archive downloads or external installs are performed by the skill itself in the instructions.

Credentials

No environment variables, credentials, or config paths are requested beyond the user skill directories. The requested file access (skill directories) is proportional to a skill-indexing tool.

Persistence & Privilege

The skill will modify a user file (~/.openclaw/skills/INDEX.md) to keep an index updated. This is within the tool's scope but is a persistent change to user files — users should be aware it writes to their home directory and consider backups or review of the index-writing logic.

Assessment

This skill is coherent for discovering and indexing skills, but before installing or running it: 1) Verify you have and trust the 'clawhub' CLI (SKILL.md calls 'clawhub search' and 'clawhub install' but the skill metadata doesn't declare that dependency). 2) Expect the skill to read SKILL.md files under several directories and to update ~/.openclaw/skills/INDEX.md — back up that file if you care about its current contents. 3) If you share the machine, confirm you are comfortable with the agent scanning the listed directories (~/.openclaw, ~/.mind_claw, ~/.codex, ~/.cursor). 4) Consider adding a small manual confirmation step before the skill overwrites INDEX.md or runs installations to avoid unexpected writes or installs.

Finds existing local skills or searches ClawHub before you build anything new.

The Problem This Solves

Skills get installed but nobody remembers what's available. This is the first skill to ask before writing a new one.

Step 1: Check Local INDEX

Read ~/.openclaw/skills/INDEX.md and search by keyword.

If a matching skill is found:

• Tell the user the skill name and what it does
• Point them to the install location

Step 2: Search ClawHub

If nothing local matches, run:

clawhub search "<task keywords>"

Present results with:

• Skill name and description
• Install command: clawhub install <name>

Step 3: Nothing Found

If neither local nor ClawHub has a match, say: "No existing skill found for this task. Building a new one is a good option."

Do NOT invent or assume a skill exists.

Keeping INDEX.md Updated

After installing any new skill, rescan and update the index:

find ~/.openclaw/skills ~/mind_claw ~/.codex/skills ~/.cursor/skills-cursor -name "SKILL.md" 2>/dev/null

Extract name and description from each SKILL.md frontmatter, then write to ~/.openclaw/skills/INDEX.md with this format:

# Skill Index

## [Category Name]
| Name | Description | Path |
|------|-------------|------|
| skill-name | What it does | /path/to/skill |

Decision Flow

User asks "I want to do XXX, what skill do I have?"

1. Read INDEX.md
2. Search for "XXX" keyword
3. If found locally: use it
4. If not found: clawhub search "XXX"
5. If on ClawHub: offer install command
6. If nowhere: suggest building one

Never Do This

• Do not assume a skill exists without checking
• Do not suggest building when ClawHub has one
• Do not leave INDEX.md stale after new installs
• Do not guess — show the index and let the user verify

Quick Reference

Situation	Action
"what skills do I have"	Show full INDEX.md
"I want to do XXX, what skill"	Search INDEX, then ClawHub
"search ClawHub for XXX"	Run clawhub search
"which skill should I use"	Read INDEX, show matches
"build a new skill"	First run skill-router to check if one exists