---
x-i18n:
  source_path: "clawhub/index.md"
summary: "Public ClawHub overview for discovery, install, publish, security, and the clawhub CLI."
read_when:
  - Explaining what ClawHub is
  - Searching for, installing, or updating skills or plugins
  - Publishing skills or plugins to the registry
  - Choosing between openclaw and clawhub CLI flows
title: "ClawHub"
sidebarTitle: "ClawHub"
---

# 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, sync, and delete/undelete workflows.

Site: [clawhub.ai](https://clawhub.ai)

## Quick start

Search and install skills with OpenClaw:

```bash
openclaw skills search "calendar"
openclaw skills install <skill-slug>
openclaw skills update --all
```

Search and install plugins with OpenClaw:

```bash
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:

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

## What ClawHub hosts

| Surface        | What it stores                                               | Typical command                              |
| -------------- | ------------------------------------------------------------ | -------------------------------------------- |
| Skills         | Versioned text bundles with `SKILL.md` plus supporting files | `openclaw skills install <slug>`             |
| Code plugins   | OpenClaw plugin packages with compatibility metadata         | `openclaw plugins install clawhub:<package>` |
| Bundle plugins | Packaged plugin bundles for OpenClaw distribution            | `clawhub package publish <source>`           |

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:

```bash
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:

```bash
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`:

```bash
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:

```bash
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](./cli.md) for the full command
reference and [Skill format](./skill-format.md) 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
[Security](./security.md),
[Security Audits](./security-audits.md),
[Moderation and Account Safety](./moderation.md), and
[Acceptable usage](./acceptable-usage.md) for policy and enforcement details.

## Telemetry and environment

When you run `clawhub install` while logged in, the CLI may send a best-effort
install event so ClawHub can compute aggregate install counts. Disable this with:

```bash
export CLAWHUB_DISABLE_TELEMETRY=1
```

Useful environment overrides:

| Variable                      | Effect                                            |
| ----------------------------- | ------------------------------------------------- |
| `CLAWHUB_SITE`                | Override the site URL used for browser login.     |
| `CLAWHUB_REGISTRY`            | Override the registry API URL.                    |
| `CLAWHUB_CONFIG_PATH`         | Override where the CLI stores token/config state. |
| `CLAWHUB_WORKDIR`             | Override the default working directory.           |
| `CLAWHUB_DISABLE_TELEMETRY=1` | Disable install telemetry.                        |

See [Telemetry](./telemetry.md), [HTTP API](./http-api.md), and
[Troubleshooting](./troubleshooting.md) for deeper reference material.