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 Analysis
medium confidenceThe 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.
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).
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.
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.
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.
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.
Guidance
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.
Latest Release
v1.1.0
English-only rewrite, removed Chinese characters, decision flow uses plain text instead of box diagrams for better visibility
More by @kennyzir
Published by @kennyzir on ClawHub