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

ClawHub

ClawHub is the public registry for OpenClaw skills and plugins.

Use native
text
openclaw
commands to search, install, and update skills, and to install plugins from ClawHub.
Use the separate
text
clawhub
CLI for registry auth, publish, delete/undelete, and sync workflows.

Site: clawhub.ai

Quick start

Search

```bash} openclaw skills search "calendar" ```

Install

```bash} openclaw skills install ```

Use

Start a new OpenClaw session — it picks up the new skill.

Publish (optional)

For registry-authenticated workflows (publish, sync, manage), install the separate `clawhub` CLI:


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

Native OpenClaw flows

```bash} openclaw skills search "calendar" openclaw skills install openclaw skills update --all ```


text
Native `openclaw` commands install into your active workspace and
persist source metadata so later `update` calls can stay on ClawHub.

```bash} openclaw plugins install clawhub: openclaw plugins update --all ```


text
Bare npm-safe plugin specs are also tried against ClawHub before npm:

```bash}
openclaw plugins install openclaw-codex-app-server
```

Use `npm:<package>` when you want npm-only resolution without a
ClawHub lookup:

```bash}
openclaw plugins install npm:openclaw-codex-app-server
```

Plugin installs validate advertised `pluginApi` and
`minGatewayVersion` compatibility before archive install runs, so
incompatible hosts fail closed early instead of partially installing
the package.

note

`openclaw plugins install clawhub:...` only accepts installable plugin families. If a ClawHub package is actually a skill, OpenClaw stops and points you at `openclaw skills install ` instead.

Anonymous ClawHub plugin installs also fail closed for private packages. Community or other non-official channels can still install, but OpenClaw warns so operators can review source and verification before enabling them.

What ClawHub is

A public registry for OpenClaw skills and plugins.
A versioned store of skill bundles and metadata.
A discovery surface for search, tags, and usage signals.

A typical skill is a versioned bundle of files that includes:

A
text
SKILL.md
file with the primary description and usage.
Optional configs, scripts, or supporting files used by the skill.
Metadata such as tags, summary, and install requirements.

ClawHub uses metadata to power discovery and safely expose skill capabilities. The registry tracks usage signals (stars, downloads) to improve ranking and visibility. Each publish creates a new semver version, and the registry keeps version history so users can audit changes.

Workspace and skill loading

The separate

text

clawhub

CLI also installs skills into

text

./skills

under your current working directory. If an OpenClaw workspace is configured,

text

clawhub

falls back to that workspace unless you override

text

--workdir

(or

text

CLAWHUB_WORKDIR

). OpenClaw loads workspace skills from

text

<workspace>/skills

and picks them up in the next session.

If you already use

text

~/.openclaw/skills

or bundled skills, workspace skills take precedence. For more detail on how skills are loaded, shared, and gated, see Skills.

Service features

Feature	Notes
Public browsing	Skills and their text `SKILL.md` content are publicly viewable.
Search	Embedding-powered (vector search), not just keywords.
Versioning	Semver, changelogs, and tags (including text `latest` ).
Downloads	Zip per version.
Stars and comments	Community feedback.
Security scan summaries	Detail pages show the latest scan state before install or download.
Scanner detail pages	VirusTotal, ClawScan, and static-analysis results have deep links.
Owner recovery dashboard	Publishers can see scan-held owned content from text `/dashboard` .
Owner-requested rescans	Owners can request limited rescans for false-positive recovery.
Moderation	Approvals and audits.
CLI-friendly API	Suitable for automation and scripting.

Security and moderation

ClawHub is open by default — anyone can upload skills, but a GitHub account must be at least one week old to publish. This slows down abuse without blocking legitimate contributors.

ClawHub CLI

You only need this for registry-authenticated workflows such as publish/sync.

Global options

Working directory. Default: current dir; falls back to OpenClaw workspace. Skills directory, relative to workdir. Site base URL (browser login). Registry API base URL. Disable prompts (non-interactive). Print CLI version.

Commands

Common workflows

```bash} clawhub search "postgres backups" ``` ```bash} clawhub package explore --family code-plugin clawhub package explore "memory" --family code-plugin clawhub package inspect episodic-claw ``` ```bash} clawhub install my-skill-pack ``` ```bash} clawhub update --all ``` ```bash} clawhub skill publish ./my-skill --slug my-skill --name "My Skill" --version 1.0.0 --tags latest ``` ```bash} clawhub sync --all ``` ```bash} clawhub package publish your-org/your-plugin --dry-run clawhub package publish your-org/your-plugin clawhub package publish your-org/your-plugin@v1.0.0 clawhub package publish https://github.com/your-org/your-plugin ```

Plugin package metadata

Code plugins must include the required OpenClaw metadata in

text

package.json


json
{
  "name": "@myorg/openclaw-my-plugin",
  "version": "1.0.0",
  "type": "module",
  "openclaw": {
    "extensions": ["./src/index.ts"],
    "runtimeExtensions": ["./dist/index.js"],
    "compat": {
      "pluginApi": ">=2026.3.24-beta.2",
      "minGatewayVersion": "2026.3.24-beta.2"
    },
    "build": {
      "openclawVersion": "2026.3.24-beta.2",
      "pluginSdkVersion": "2026.3.24-beta.2"
    }
  }
}

Published packages should ship built JavaScript and point

text

runtimeExtensions

at that output. Git checkout installs can still fall back to TypeScript source when no built files exist, but built runtime entries avoid runtime TypeScript compilation in startup, doctor, and plugin loading paths.

Versioning, lockfile, and telemetry

Environment variables

Variable	Effect
text `CLAWHUB_SITE`	Override the site URL.
text `CLAWHUB_REGISTRY`	Override the registry API URL.
text `CLAWHUB_CONFIG_PATH`	Override where the CLI stores the token/config.
text `CLAWHUB_WORKDIR`	Override the default workdir.
text `CLAWHUB_DISABLE_TELEMETRY=1`	Disable telemetry on text `sync` .

OpenClaw Docs

ClawHub

Quick start

Search

Install

Use

Publish (optional)

Native OpenClaw flows

note

What ClawHub is

Workspace and skill loading

Service features

Security and moderation

ClawHub CLI

Global options

Commands

Common workflows

Plugin package metadata

Versioning, lockfile, and telemetry

Environment variables

Related