Find the Right OpenClaw Skill in a Curated Directory of 5,300+

OpenClaw's public registry, ClawHub, hosts thousands of community-built skills — and, like any open registry, thousands of entries you would not want to install. VoltAgent/awesome-openclaw-skills, at 53k stars, is the curated layer on top: the README's header invites you to discover over 5,300 community-built OpenClaw skills, organized by category.

Why This Skill Matters

OpenClaw is a locally-running AI assistant that operates directly on your machine, and skills extend what it can do — talk to external services, automate workflows, perform specialized tasks. The list sources every entry from ClawHub and sorts them into 30 categories. The largest are Coding Agents & IDEs (1,184 skills), Web & Frontend Development (920), DevOps & Cloud (393), Search & Research (343), and Browser & Automation (323).

Curation is the real product. The README documents 7,215 registry entries it did not take: 4,065 excluded as possibly spam (bulk accounts, bot accounts, test/junk), 1,040 as duplicate or similar-name, 851 for low-quality or non-English descriptions, 886 for crypto, blockchain, finance, or trade topics, and 373 as malicious — identified by security audits published by researchers. The list also only accepts skills already published on ClawHub, so every entry points at a registry-managed install.

Installation

The plainest path is the OpenClaw CLI:

openclaw skills install <skill-slug>

If you want registry-managed skill folders outside a full OpenClaw workspace, use the ClawHub CLI:

npx clawhub install <skill-slug>

Manual installation copies the skill folder to ~/.openclaw/skills/ (global) or <project>/skills/ (workspace). The README's priority line: Workspace > Local > Bundled.

Real Workflow: Install a Skill From a Category

1. Browse the README's table of contents and open the category matching your task — each links to a full listing file, for example categories/git-and-github.md.
2. Pick a skill and copy its ClawHub slug, then install:

openclaw skills install <skill-slug>

3. For a concrete example of the command shape, the README's security-auditing section documents exactly this form for trentclaw, which audits your OpenClaw config, installed skills, and custom code:

openclaw skills install trentclaw

Real Workflow: Let Your Assistant Do the Setup

The README documents a lower-friction alternative: paste the skill's GitHub repository link directly into your assistant's chat and ask it to use the skill. The assistant handles the setup in the background — useful when you are already mid-conversation and just want one more capability.

Tips

• Treat the list as curated, not audited — the README says so in its security notice. OpenClaw has a VirusTotal partnership: visit a skill's page on ClawHub and check the VirusTotal report before installing.
• The notice also recommends two scanning tools: the Snyk Skill Security Scanner (snyk/agent-scan) and the Agent Trust Hub.
• To get your own skill listed, publish it on ClawHub first — the list does not accept personal repos or gists, and your PR must include the ClawHub link.
• Skills can be updated, modified, or replaced by their maintainers after being listed, so re-check anything you installed a while ago.

When Not to Use This

The collection is OpenClaw-specific: install paths run through the openclaw and clawhub CLIs and land in ~/.openclaw/ directories, so skills for other agent runtimes need a compatibility check of their own. And if you need vetted, first-party integrations rather than community picks, a vendor's official catalog is the safer starting point — this list optimizes for breadth.

See the leaderboard for more skills.