ClawHub Public Repository for OpenClaw Skills and Plugins

ClawHub

ClawHub serves as the public repository for OpenClaw skills and plugins.

• Search, install, and update skills, along with plugin installation from ClawHub, are handled through native openclaw commands.
• For registry authentication, publishing, and delete or undelete operations, use the separate clawhub CLI.

Website: clawhub.ai

Quick start

Use OpenClaw to search for and install skills:

openclaw skills search "calendar"
openclaw skills install @openclaw/demo
openclaw skills update --all

Use OpenClaw to search for and install plugins:

openclaw plugins search "calendar"
openclaw plugins install clawhub:<package>
openclaw plugins update --all

When registry-authenticated workflows like publishing or delete/undelete are needed, install the ClawHub CLI:

npm i -g clawhub
# or
pnpm add -g clawhub

What ClawHub hosts

ClawHub keeps track of semver versions, tags like latest, changelogs, files, downloads, stars, and security scan summaries. Public pages display the current registry state, allowing users to review a skill or plugin before installation.

Native OpenClaw flows

Native OpenClaw commands install into the active OpenClaw workspace and retain source metadata so that subsequent update commands can remain linked to ClawHub.

When a plugin installation should resolve through ClawHub, use clawhub:<package>. Bare npm-safe plugin specifications may resolve through npm during launch transitions, and npm:<package> stays npm-only when a source must be explicitly stated.

Plugin installations check the advertised pluginApi and minGatewayVersion compatibility before the archive install proceeds. If a package version publishes a ClawPack artifact, OpenClaw prefers the exact uploaded npm-pack .tgz, verifies the ClawHub digest header and downloaded bytes, and records artifact metadata for future updates.

ClawHub CLI

The ClawHub CLI is intended for registry-authenticated tasks:

clawhub login
clawhub whoami
clawhub search "postgres backups"
clawhub skill publish ./my-skill --slug my-skill --name "My Skill" --version 1.0.0
clawhub package explore --family code-plugin
clawhub package inspect episodic-claw
clawhub package publish your-org/your-plugin --dry-run
clawhub package publish your-org/your-plugin

For direct registry workflows, the CLI also provides skill install and update commands:

clawhub install @openclaw/demo
clawhub update @openclaw/demo
clawhub update --all
clawhub list

These commands install skills into ./skills beneath the current working directory and record installed versions in .clawhub/lock.json.

Publishing

Publish skills from a local folder that contains SKILL.md:

clawhub skill publish <path>

Common options for publishing:

• --slug <slug>: the URL name of the published skill.
• --name <name>: the display name.
• --version <version>: the semver version.
• --changelog <text>: the changelog text.
• --tags <tags>: tags separated by commas, defaulting to latest.

Publish plugins from a local folder, owner/repo, owner/repo@ref, or a GitHub URL:

clawhub package publish <source>

To build the exact publish plan without uploading, use --dry-run; for CI-friendly output, use --json.

Code plugins must contain the required OpenClaw compatibility metadata in package.json, which includes openclaw.compat.pluginApi and openclaw.build.openclawVersion. Refer to the CLI for the full command reference and Skill format for skill metadata.

Security and moderation

ClawHub is open by default: anyone can upload, but a GitHub account old enough to pass the upload gate is required for publishing. Public detail pages summarize the latest scan state before an install or download.

Automated checks run on published skills and plugin releases. Releases that are scan-held or blocked may be removed from public catalog and install surfaces, though they remain visible to their owner in /dashboard.

Users who are signed in can report skills and packages. Moderators have the ability to review reports, hide or restore content, and ban abusive accounts. For policy and enforcement details, see Security, Security Audits, Moderation and Account Safety, and Acceptable usage.

Telemetry and environment

When logged in and running clawhub install, the CLI may send a best-effort install event so ClawHub can calculate aggregate install counts. To disable this, use:

export CLAWHUB_DISABLE_TELEMETRY=1

Useful environment overrides:

For more detailed reference content, refer to the documentation on Telemetry, HTTP API, and Troubleshooting.