What is ClawHub? OpenClaw's skill registry, explained

What it is, precisely

ClawHub is to OpenClaw skills roughly what npm is to JavaScript packages: the shared public shelf. Anyone can publish; everything is public and visible; installing is one command. It’s an official part of the OpenClaw ecosystem (the registry code lives in the openclaw GitHub organization), but official registry does not mean vouched-for contents, any more than npm’s existence vouches for every package on it. That single distinction organizes everything else worth knowing.

ClawHub does check what it hosts. Every published skill and plugin release gets an automated security audit, shown on its page before you install as Pass, Review, Warn or Malicious (“Do not install”), or as Pending or Error while a scan hasn’t finished, and a release a scan holds back can drop out of search and install. Its own docs are careful about what that buys: “Audits are strong safety signals, but they are not a guarantee that a release is risk-free.”

Using it

openclaw skills search <keyword>                 # find skills in the registry
openclaw skills install @owner/name              # install one
openclaw skills install @owner/name --version <v> # install a pinned version

# or the standalone CLI:
clawhub install <skill>
clawhub pin <skill>       clawhub unpin <skill>
clawhub list              clawhub update --all
clawhub uninstall <skill>

Installs land in your workspace’s skills directory (or ./skills where no workspace is configured), which means installed skills are part of the state you back up, and you can open any of them and read exactly what they tell your agent to do.

The supply-chain caution, plainly

An open registry for agent instructions is a new kind of supply chain, and 2026 has already demonstrated the failure mode: security researchers auditing community skill registries found real malware among the listings, instructions crafted to exfiltrate data or misuse the agent’s capabilities, dressed as productivity skills. This isn’t a reason to avoid ClawHub; it’s a reason to use it the way experienced developers use npm:

• Skim before you install. A skill is a readable markdown file. If you wouldn’t paste its instructions into your agent’s chat yourself, don’t install it.
• Prefer known publishers and pin versions (--version, or clawhub pin): an update you didn’t review is an install you didn’t review. The built-in audit holds plugins and hooks to the same rule, flagging any installed from an unpinned version.
• Keep the blast radius small. Registry skills plus an agent on your personal laptop multiply each other’s risks; the same skills on a dedicated machine are a contained experiment.

Three skills you’ve read beat thirty you haven’t. The registry is one of OpenClaw’s superpowers. It just deserves the same adult respect as every other place strangers publish code.