Find Skills
Discover and install skills from the open agent skills ecosystem at https://skills.sh/
Finding Skills
Search using the CLI:
npx skills find [query]Or browse https://skills.sh/ directly.
Installing a Skill As-Is
Use npx skills add to a temp directory (it handles repo cloning and path resolution internally — skill paths vary wildly across repos), then move the result to the correct OpenClaw location.
Step 1: Ask the user
Before installing, always ask:
- Do you want to install this?
- Should it be available to all agents or a specific agent?
Step 2: Install to temp dir and move
# Install to temp dir (the CLI resolves the correct path within the repo)
cd /tmp && mkdir -p skill-tmp && cd skill-tmp
npx skills add <owner/repo@skill-name> -y
# Move to the correct OpenClaw location
cp -r .agents/skills/<skill-name> <TARGET_DIR>/<skill-name>
# Clean up
rm -rf /tmp/skill-tmpTarget directories:
| Scope | Location |
|---|---|
| All agents (global) | /root/.openclaw/skills/<skill-name>/ |
| Specific agent | /root/.openclaw/workspace-<agent>/skills/<skill-name>/ |
| Main agent only | /root/.openclaw/workspace/skills/<skill-name>/ |
Step 3: Verify
openclaw skills info <skill-name>Note: Skills are snapshotted at session start. The user needs a new session (/new) for newly installed skills to appear.
Building Your Own Skill (Recommended)
Often the best approach is not to install an existing skill directly, but to use them as research to build a better one:
- Search for relevant skills with
npx skills find [query] - Fetch a few of the top results to a temp dir (see above) and read their SKILL.md files
- Compare — identify what's good, what's missing, what's redundant or too generic
- Build your own that combines the best parts, adds missing pieces, and is tailored to your actual workflow
This is usually better than installing someone else's skill because:
- Community skills vary wildly in quality (some are just vague guidelines, others have real code)
- Your needs are specific — a generic skill won't cover your stack/tools/patterns
- You can keep it focused and practical instead of trying to cover everything
- You own it and can iterate on it
Workflow
npx skills find "chrome extension"
→ Found 6 results
Install top 3 to /tmp, read their SKILL.md files
→ mindrally: guidelines only, no code examples
→ tenequm: WXT framework focused, good modern tooling coverage
→ dicklesworthstone: Claude browser automation, not what we need
Write your own combining the best parts
→ Save to the appropriate OpenClaw skills directoryWhen No Skills Are Found
If no relevant skills exist, consider building one from scratch using the skill-creator skill, or help the user solve their problem directly.