Every OpenClaw agent starts as a blank slate—capable of chat and reasoning, but useless for your actual stack until you teach it something. ClawHub is the public registry solving that problem, acting as a versioned, searchable library where you install agent capabilities like you'd install an npm package. One command to add a skill, one command to update it, and your agent gains a new ability without touching code.
What a Skill Actually Is
A skill is a versioned bundle that teaches your agent how to perform specific tasks. The core is always a SKILL.md file—a markdown document describing what the skill does, when to use it, and how to execute it. That file gets injected into the agent's system context as structured instructions. Beyond that, skills can include supporting scripts (shell, Python, Node), config templates, and metadata controlling when they load. The composability is the point: five well-chosen skills make an agent dramatically more useful than none.
Searching and Installing
The registry lives at clawhub.ai with full searchable listings. From the terminal, OpenClaw's native search uses vector embeddings rather than keyword matching—search by what you want to accomplish ("calendar management") not what you think the skill is named. Installation is straightforward: openclaw skills install fetches the latest version into your workspace's skills/ directory. The ClawHub CLI offers more control for specific versions (--version 1.2.0) or forced overwrites (--force). All installed skills get recorded in .clawhub/lock.json, giving you a package-lock-style audit trail.
Publishing and Versioning
Here's where ClawHub becomes genuinely useful for dev teams: publish your own skills to share them or back them up. The clawhub sync command scans local skills, compares against the registry via content hash, and uploads anything new or changed. Each publish creates a semver version automatically. There's a minimal spam throttle—GitHub accounts must be one week old to publish—but otherwise the barrier is low. Skills with more than three user reports get auto-hidden pending moderation, which keeps the registry usable without gatekeeping.
Practical Patterns Worth Knowing
Search by intent, not keywords. Vector search means "automate my standup" surfaces relevant skills even without exact phrase matches. Always inspect SKILL.md before installing—vague docs or unusual permission requests should give you pause. For production setups, pin versions by committing .clawhub/lock.json to version control; it gives reproducible installs and a clear audit trail when behavior changes. Run clawhub sync --dry-run before publishing to catch accidental inclusions.
The Bottom Line
ClawHub isn't just a library—it's a distribution channel for agent capabilities. If you're building OpenClaw setups for clients or teams, this is how you distribute exactly what each agent needs. Publish once, install everywhere, update from a single source of truth. The registry gets more useful as it grows, and that growth depends on people publishing what they build. Don't overthink it—just publish.