Skill Router Pro

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

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