ClawHub Skill Registry: Discover and Install 5,700+ OpenClaw Skills

ClawHub Registry is the npm for OpenClaw. It is the fourth most popular skill in the ecosystem with 910 stars, and it provides a centralized marketplace where you can search, install, update, and manage over 5,700 community-contributed skills from your chat interface. Instead of manually downloading dependencies, configuring permissions, and tracking updates across dozens of skills, ClawHub handles version resolution, security verification, and installation in a single command.

This guide covers the complete lifecycle: how to search for skills, evaluate them for safety and compatibility, install them with automatic dependency resolution, manage updates, and publish your own skills to the registry. If you are scaling your OpenClaw deployment and need to standardize your skill stack across multiple agents, ClawHub is the infrastructure layer that makes skill management practical at scale.

What ClawHub Provides

ClawHub is a centralized skill catalog built on the same model as language package managers. It aggregates skills from hundreds of contributors, tracks dependencies between skills, manages version compatibility, and provides security verification badges so you can evaluate trust before installation.

The registry solves five problems that appear once your OpenClaw instance grows beyond a handful of manually-installed skills:

Centralized skill catalog — All available skills in one searchable index. Instead of hunting through GitHub repositories, documentation sites, and community Discord threads, you query ClawHub from your chat interface and see results ranked by relevance, popularity, and compatibility with your platform.

Dependency resolution — Many skills depend on other skills. The GitHub Issue Triage skill requires the GitHub API skill, which requires the HTTP client skill. ClawHub detects these dependencies automatically and installs the full chain in the correct order. Manual dependency management fails once your skill count crosses ten.

Version management — Skills evolve. Breaking changes happen. ClawHub tracks version compatibility so you can pin specific versions for production stability or automatically update to the latest release for development instances. It also checks whether the skill version you are installing is compatible with your OpenClaw version.

Security and verification badges — Not all community skills are equally trustworthy. ClawHub marks skills as Official (published by the OpenClaw team), Verified (code-reviewed by trusted maintainers), or Community (use at your own risk). This prevents a common failure mode where teams install an unvetted skill that exfiltrates credentials or consumes excessive API quota.

Skill ratings and reviews — Download counts, star ratings, and written reviews help you distinguish between actively maintained skills with responsive maintainers and abandoned projects that no longer work with current OpenClaw versions. Popularity is not a perfect signal, but it filters out dead code.

ClawHub is itself an OpenClaw skill, which means updates to the registry system are delivered through the same mechanism it manages. This makes the entire ecosystem self-hosting and avoids fragmentation across different package manager implementations.

Installation

Installing ClawHub is a one-time setup step. Once it is installed, all future skill operations go through ClawHub instead of manual file copying or Git cloning.

openclaw skill install clawhub-registry

On first run, ClawHub prompts for configuration:

ClawHub Registry installed successfully.

Initial setup:
- Registry URL: https://registry.clawhub.io (default)
- Update channel: stable / beta / nightly
- Auto-update: enabled / disabled
- Verification policy: strict / permissive / off

Most users should choose the stable update channel and enable auto-update. The strict verification policy blocks installation of any skill that does not have at least a Verified badge, which is useful for production deployments. Permissive allows Community skills with a confirmation prompt. Turning verification off is not recommended unless you are testing local development skills.

Authentication is optional unless you plan to publish skills to the registry. For browsing and installing, ClawHub works unauthenticated. If you want to publish your own skills, run:

openclaw clawhub login

This opens a browser to authenticate via GitHub OAuth. Your API token is stored locally and never transmitted to third parties. Publishing permissions are scoped to your own namespace, so you cannot overwrite or hijack skills published by other users.

After installation, verify that ClawHub is working:

Search ClawHub for calendar

If you see a list of calendar-related skills with install commands, setup is complete.

Searching for Skills

ClawHub supports five search modes: keyword, category, compatibility, popularity, and verification level. Most searches start with a keyword query and then refine using filters.

By keyword — The simplest search. Ask for skills related to a concept or tool:

Search ClawHub for calendar
Search ClawHub for GitHub automation
Search ClawHub for Docker monitoring

Results are ranked by relevance (how well the skill description matches your query), weighted by popularity. A skill with 1,000 downloads that matches your query loosely will rank below a skill with 10,000 downloads that matches tightly.

By category — Skills are tagged with primary categories. This is useful for browsing when you know the domain but not the specific tool:

Show me productivity skills in ClawHub
List all development skills
Browse automation skills

Categories are not mutually exclusive. The Linear Integration skill appears in both Productivity and Development because it handles both task management and developer workflows.

By compatibility — Filter by platform, OpenClaw version, or required dependencies. This prevents wasting time on skills that will not work in your environment:

Search ClawHub for Docker skills compatible with macOS
Find skills that work with OpenClaw 0.9+

Compatibility filters are based on metadata provided by skill authors. Not all skills declare platform compatibility, so absence of a compatibility tag does not mean the skill will not work.

By popularity — Sort by stars, downloads, or recent activity:

Show me the top 10 most popular skills
What are the most downloaded skills this month?

Popularity is a trailing indicator. New skills with excellent functionality but low download counts will rank poorly. Use popularity for discovering proven, widely-used skills, not for finding cutting-edge tools.

By verification — Filter to only Official or Verified skills:

Search ClawHub for verified calendar skills
Show me official OpenClaw skills

This is the recommended approach for production deployments where security and stability are more important than access to the latest experimental features.

Skill Information

Before installing a skill, review its metadata to confirm compatibility, understand required permissions, and check whether dependencies are acceptable.

Show me details for github-issue-triage

ClawHub returns a structured summary:

Skill: GitHub Issue Triage
Version: 2.1.4
Author: OpenClaw Team
Verification: Official
Stars: 1,203
Downloads: 45,230

Description:
Automatically classify, label, and route GitHub issues based on content analysis.

Dependencies:
- github-api (>= 3.0.0)
- http-client (>= 1.5.0)

Required Permissions:
- GitHub: read:issues, write:labels
- Network: outbound HTTPS to api.github.com

Platform Compatibility:
- OpenClaw: 0.8.0+
- OS: Linux, macOS, Windows
- Runtime: Node.js 18+

Documentation: https://docs.clawhub.io/skills/github-issue-triage
Repository: https://github.com/openclaw/skills/github-issue-triage

Dependencies are listed with version constraints. ClawHub will install these automatically unless you have conflicting versions already installed.

Required permissions follow a least-privilege model. Skills declare exactly what access they need. If a calendar skill asks for GitHub API access, that is a red flag.

Platform compatibility prevents installation failures. If a skill requires Docker but you are running OpenClaw on a Raspberry Pi without Docker installed, ClawHub will warn you before installation.

Version history is available for all skills:

Show me version history for github-issue-triage

This lists all released versions, breaking changes, and upgrade notes. Use this to decide whether to pin to a specific version or stay on the latest release.

Documentation links point to skill-specific guides, API references, and example configurations. Always read the documentation before installing a skill that will handle production data or interact with external APIs.

Installing Skills

Once you have identified a skill to install, installation is a single command:

Install github-issue-triage from ClawHub

ClawHub performs dependency resolution, downloads the skill and all required dependencies, prompts for configuration values, and runs post-install setup steps automatically.

Dependency auto-resolution — If the skill depends on other skills, ClawHub installs them first:

Installing github-issue-triage...

Resolving dependencies:
- github-api 3.2.1 (required by github-issue-triage)
- http-client 1.6.0 (required by github-api)

Installing http-client 1.6.0... done
Installing github-api 3.2.1... done
Installing github-issue-triage 2.1.4... done

Configuration prompts — Most skills require API keys, webhook URLs, or other configuration values. ClawHub prompts for these during installation:

github-issue-triage configuration:

GitHub Personal Access Token: [paste token here]
Default repository (optional): owner/repo
Auto-label threshold (0.0-1.0): 0.85

Configuration saved to ~/.openclaw/skills/github-issue-triage/config.yaml

Configuration is stored locally. ClawHub never transmits your API keys to the registry server.

Post-install setup — Some skills need initialization steps like creating database tables, registering webhooks, or running schema migrations. ClawHub executes these automatically:

Running post-install setup...
- Created label taxonomy in GitHub repository
- Registered webhook at https://your-domain.com/webhooks/github
- Initialized local cache database

Installation complete. Try: "Triage my GitHub issues"

If post-install setup fails, ClawHub rolls back the installation to prevent partial state.

Managing Installed Skills

After installation, ClawHub provides commands for listing, updating, and removing skills.

List installed skills:

List my installed skills

This shows all currently installed skills with versions and update availability:

Installed skills (12):

github-issue-triage 2.1.4 (latest)
calendar-scheduler 1.3.2 (update available: 1.4.0)
linear-integration 0.9.1 (latest)
...

Checking for updates:

Check for skill updates

ClawHub queries the registry for newer versions of all installed skills and reports which have updates available. It respects your update channel setting (stable, beta, or nightly).

Bulk updating:

Update all skills

This updates every skill to the latest version on your selected channel. For production deployments, prefer updating skills individually after testing in a staging environment. Bulk updates are safe for personal instances where downtime is acceptable.

Uninstalling skills:

Uninstall calendar-scheduler

ClawHub checks for reverse dependencies before uninstalling. If another skill depends on the one you are removing, it warns you and blocks the uninstall unless you force it:

Warning: The following skills depend on calendar-scheduler:
- meeting-notes-generator

Uninstall anyway? (yes/no)

Troubleshooting conflicts — Occasionally two skills require incompatible versions of the same dependency. ClawHub detects this during installation and suggests resolution strategies:

Conflict detected:
- skill-a requires http-client >= 1.5.0, < 2.0.0
- skill-b requires http-client >= 2.0.0

Resolution options:
1. Update skill-a to version 3.0.0 (supports http-client 2.x)
2. Downgrade skill-b to version 1.2.0 (supports http-client 1.x)
3. Cancel installation

Choose option (1/2/3):

This is rare in practice because most skill authors coordinate major version bumps through the ClawHub community channels.

Skill Categories

ClawHub organizes skills into seven primary categories. These categories are not strict silos, but they help with discovery and curation.

Development — Tools for software engineering workflows. The GitHub Issue Triage skill automates issue classification and routing. The Linear Integration skill syncs tasks between Linear and OpenClaw. Git automation skills handle commits, pull requests, and branch management. Code review skills analyze diffs and suggest improvements.

Productivity — Personal and team efficiency tools. The Calendar Scheduler skill books meetings across timezones. Task management skills integrate with Todoist, Things, and Notion. Note-taking skills capture ideas and sync to Obsidian or Roam. Time tracking skills log how you spend your day.

Automation — Trigger-based workflows and integrations. The Home Assistant skill controls smart home devices. Zapier integration skills connect to thousands of third-party services. Webhook skills respond to external events. Cron scheduler skills run recurring tasks at specified intervals.

Data and Analytics — Research, finance, and business intelligence. The Finance News Briefings skill summarizes market data. The FEC Campaign Finance skill tracks political donations. Research paper skills fetch and summarize academic publications. CSV and database query skills analyze structured data.

Operations — Infrastructure management and monitoring. The Cloudflare Manager skill configures DNS, firewall rules, and caching. Docker skills monitor containers and manage deployments. Log aggregation skills ingest and analyze logs from multiple sources. Uptime monitoring skills alert on service failures.

Communication — Messaging and collaboration. Voice synthesis skills generate audio from text. The Live Canvas A2UI skill creates interactive visual interfaces. Email skills send and parse messages. Slack and Discord integration skills manage channels and notifications.

Utilities — Cross-cutting tools that do not fit other categories. The Conventional Commits skill formats commit messages. File management skills organize and tag documents. Search skills index and retrieve information from local files. Backup skills archive data to cloud storage.

When browsing by category, start broad and filter by popularity or verification level to find the most reliable skills.

Publishing Your Own Skills

If you have built a skill that solves a problem other OpenClaw users face, publishing it to ClawHub makes it discoverable and installable for the entire community. The publishing process involves five steps: create the skill, test it locally, package it for distribution, submit it to the registry, and maintain it over time.

Creating a skill — Skills are structured projects with a manifest file, source code, and documentation. The manifest declares metadata (name, version, description, dependencies, permissions), entry points, and configuration schema. Use the skill template to start:

openclaw skill create my-new-skill

This generates a skeleton with the required directory structure and boilerplate code.

Testing locally — Before publishing, install the skill on your own OpenClaw instance and verify it works:

openclaw skill install ./my-new-skill

This performs a local installation without uploading to the registry. Test all functionality, edge cases, and error handling. Check that configuration prompts are clear and that documentation is complete.

Publishing to ClawHub — Once testing is complete, publish the skill:

openclaw clawhub publish ./my-new-skill

This uploads the skill package to the registry, validates the manifest, and assigns a unique identifier. The skill is immediately available in search results, but it starts with a Community verification level. To earn a Verified badge, request a code review from ClawHub maintainers via the community Discord.

Verification process — Verified skills undergo a security and quality review. Maintainers check for common issues: hardcoded credentials, excessive permissions, missing error handling, unclear documentation, and dependency conflicts. The review typically takes 3-5 days. Official status is reserved for skills published by the OpenClaw core team.

Maintenance best practices — After publishing, monitor GitHub issues and respond to user questions. Release updates to fix bugs and add features. Follow semantic versioning so users know whether an update contains breaking changes. If you can no longer maintain the skill, transfer ownership to another contributor or archive it to prevent confusion.

Publishing extends the ecosystem. If your skill gets traction, it may become the de facto standard for its category, which means thousands of users depend on your code. Take that responsibility seriously.

Security and Verification

ClawHub uses a three-tier verification system to help users evaluate trust before installation.

Official skills — Published and maintained by the OpenClaw core team. These skills undergo the most rigorous review and are kept up-to-date with the latest OpenClaw versions. Examples: GitHub Issue Triage, Calendar Scheduler, Linear Integration. Install Official skills with high confidence.

Verified skills — Published by community contributors but reviewed by ClawHub maintainers. Verification confirms that the skill follows security best practices: no hardcoded secrets, appropriate permission scoping, input validation, error handling, and clear documentation. Verified does not mean bug-free, but it means the skill has been read by trusted reviewers. Most production deployments should limit installations to Official and Verified skills.

Community skills — Published by anyone, no review required. These skills are not inherently unsafe, but they have not been audited. Use Community skills for experimentation, development environments, or when the functionality is niche enough that no Verified alternative exists. Always review the source code before installing a Community skill that will access production credentials or handle sensitive data.

Permission model — Skills declare required permissions in their manifest. ClawHub enforces these permissions at runtime, so a skill that declares only file system access cannot make network requests without triggering a security violation. Permissions are scoped narrowly: a skill can request GitHub read access without also getting write access. Review the permission list before installation and deny any skill that asks for more access than its functionality requires.

Sandboxing — ClawHub runs skills in isolated environments with limited access to the host system. Skills cannot read arbitrary files, execute system commands, or modify OpenClaw’s core configuration unless they explicitly request those permissions and the user approves. This prevents a compromised skill from escalating privileges or exfiltrating data from other skills.

For production deployments, configure ClawHub with strict verification policy and regularly audit installed skills for updates and security advisories.

FAQ

Are ClawHub skills free?

Most skills are free and open-source under permissive licenses like MIT or Apache 2.0. A small number of skills are commercial and require a paid subscription or API key from the skill publisher. ClawHub marks commercial skills clearly in search results. The registry itself is free to use for browsing, installing, and publishing skills. There are no fees for hosting open-source skills on ClawHub.

How do I know if a skill is safe to install?

Start by checking the verification badge. Official and Verified skills have undergone code review. For Community skills, read the source code if you have the expertise, or check the skill’s GitHub repository for stars, issues, and recent commits. A skill with 1,000+ downloads, active issue discussions, and frequent updates is more trustworthy than one with 10 downloads and no activity in six months. Review the requested permissions. If a skill asks for more access than its functionality requires, that is a warning sign. When in doubt, test the skill in a sandboxed development instance before installing it in production.

Can I create private skill registries?

Yes. ClawHub supports self-hosted registries for teams that need to distribute internal skills without publishing them to the public registry. Set up a private registry server using the ClawHub Registry self-hosting guide, then configure your OpenClaw instances to point to the private registry URL. This is common for enterprises with proprietary workflows, compliance requirements, or air-gapped deployments. Private registries have the same features as the public registry: dependency resolution, version management, and verification workflows.

---

ClawHub turns skill management from a manual file-copying process into a structured package ecosystem. As your OpenClaw deployment grows, the registry becomes essential infrastructure. Start by browsing Official and Verified skills, install a few that match your workflows, and contribute back to the ecosystem by publishing your own skills when you build something reusable.

For deeper skill integration strategies, see the Docker 24/7 deployment guide and the internal knowledge base guide. Join the community Discord to discuss skill development, request features, and share your own ClawHub discoveries.