Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.openclaw.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
ClawHub

ClawHub is the public registry for OpenClaw skills and plugins.
  • Use native openclaw commands to search, install, and update skills and to install plugins from ClawHub.
  • Use the separate clawhub CLI for registry auth, publishing, delete/undelete, and sync workflows.
Site: clawhub.ai

​
Quick start

Search and install skills with OpenClaw: 
openclaw skills search "calendar"
openclaw skills install <skill-slug>
openclaw skills update --all
Search and install plugins with OpenClaw: 
openclaw plugins search "calendar"
openclaw plugins install clawhub:<package>
openclaw plugins update --all
Install the ClawHub CLI when you want registry-authenticated workflows such as publish, sync, or delete/undelete: 
npm i -g clawhub
# or
pnpm add -g clawhub

​
What ClawHub hosts

SurfaceWhat it storesTypical command
SkillsVersioned text bundles with SKILL.md plus supporting filesopenclaw skills install <slug>
Code pluginsOpenClaw plugin packages with compatibility metadataopenclaw plugins install clawhub:<package>
Bundle pluginsPackaged plugin bundles for OpenClaw distributionclawhub package publish <source>
SoulsSOUL.md bundles shown on onlycrabs.aiWeb and API publish flows
ClawHub tracks semver versions, tags such as latest, changelogs, files, downloads, stars, and security scan summaries. Public pages show current registry state so users can inspect a skill or plugin before installing it.

​
Native OpenClaw flows

Native OpenClaw commands install into the active OpenClaw workspace and persist source metadata so later update commands can stay on ClawHub. Use clawhub:<package> when a plugin install should resolve through ClawHub. Bare npm-safe plugin specs may resolve through npm during launch cutovers, and npm:<package> stays npm-only when a source must be explicit. Plugin installs validate advertised pluginApi and minGatewayVersion compatibility before archive install runs. When 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 later updates.

​
ClawHub CLI

The ClawHub CLI is for registry-authenticated work: 
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
clawhub sync --all
The CLI also has skill install/update commands for direct registry workflows: 
clawhub install <slug>
clawhub update <slug>
clawhub update --all
clawhub list
Those commands install skills into ./skills under the current working directory and record installed versions in .clawhub/lock.json.

​
Publishing

Publish skills from a local folder containing SKILL.md: 
clawhub skill publish <path>
Common publish options:
  • --slug <slug>: skill slug.
  • --name <name>: display name.
  • --version <version>: semver version.
  • --changelog <text>: changelog text.
  • --tags <tags>: comma-separated tags, defaulting to latest.
Publish plugins from a local folder, owner/repo, owner/repo@ref, or a GitHub URL: 
clawhub package publish <source>
Use --dry-run to build the exact publish plan without uploading, and --json for CI-friendly output. Code plugins must include the required OpenClaw compatibility metadata in package.json, including openclaw.compat.pluginApi and openclaw.build.openclawVersion. See CLI for the full command reference and Skill format for skill metadata.

​
Security and moderation

ClawHub is open by default: anyone can upload, but publishing requires a GitHub account old enough to pass the upload gate. Public detail pages summarize the latest scan state before install or download. ClawHub runs automated checks on published skills and plugin releases. Scan-held or blocked releases may disappear from public catalog and install surfaces while remaining visible to their owner in /dashboard. Signed-in users can report skills and packages. Moderators can review reports, hide or restore content, and ban abusive accounts. See Acceptable usage and Security + moderation for policy and enforcement details.

​
Telemetry and environment

When you run clawhub sync while logged in, the CLI sends a minimal snapshot so ClawHub can compute install counts. Disable this with: 
export CLAWHUB_DISABLE_TELEMETRY=1
Useful environment overrides:
VariableEffect
CLAWHUB_SITEOverride the site URL used for browser login.
CLAWHUB_REGISTRYOverride the registry API URL.
CLAWHUB_CONFIG_PATHOverride where the CLI stores token/config state.
CLAWHUB_WORKDIROverride the default working directory.
CLAWHUB_DISABLE_TELEMETRY=1Disable telemetry on sync.
See Telemetry, HTTP API, and Troubleshooting for deeper reference material.