Quickstart: Find, Install, Update, and Publish Skills or Plugins with ClawHub

Quickstart

ClawHub is a registry for OpenClaw skills and plugins.

When installing items into OpenClaw, use OpenClaw itself. Use the clawhub CLI for signing in, publishing, managing your own listings, or working with registry-specific workflows.

Find and install a skill

Search from OpenClaw:

openclaw skills search "calendar"

Install a skill:

openclaw skills install @openclaw/demo

Update installed skills:

openclaw skills update --all

OpenClaw remembers the source of each skill so future updates can still resolve through ClawHub.

Find and install a plugin

Search from OpenClaw:

openclaw plugins search "calendar"

Install a ClawHub-hosted plugin by specifying a ClawHub source:

openclaw plugins install clawhub:<package>

Update installed plugins:

openclaw plugins update --all

Use the clawhub: prefix to tell OpenClaw to resolve the package through ClawHub instead of npm or another source.

Sign in for publishing

Install the ClawHub CLI:

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

Sign in with GitHub:

clawhub login
clawhub whoami

Headless environments can use an API token from the ClawHub web UI:

clawhub login --token clh_...

Publish a skill

A skill is a folder containing a required SKILL.md file and optional supporting files.

clawhub skill publish ./my-skill \
  --slug my-skill \
  --name "My Skill" \
  --changelog "Initial release"

The command skips unchanged content. New skills start at 1.0.0; later changes automatically publish the next patch version. Use --dry-run to preview or --version to specify an explicit version.

Before publishing, review the metadata in SKILL.md. Declare required environment variables, tools, and permissions so users know what the skill needs before installing. See Skill format.

For repositories with multiple skills, the reusable GitHub workflow runs skill publish for each immediate skill folder under skills/:

jobs:
  preview:
    uses: openclaw/clawhub/.github/workflows/skill-publish.yml@main
    with:
      dry_run: true

Publish a plugin

Publish a plugin from a local folder, a GitHub repo, a GitHub ref, or an existing archive:

clawhub package publish <source> --family code-plugin --dry-run
clawhub package publish <source> --family code-plugin

Use --dry-run first to preview the resolved package metadata, compatibility fields, source attribution, and upload plan without publishing.

Code plugins must include OpenClaw compatibility metadata in package.json, including openclaw.compat.pluginApi and openclaw.build.openclawVersion.

Inspect before installing

Before installing, inspect metadata, source links, versions, changelogs, and scan status using the ClawHub web page or CLI detail commands:

clawhub inspect @openclaw/demo
clawhub package inspect <package>

Public listings show the latest scan state. Releases that are held or blocked by moderation may be hidden from search and install surfaces until resolved.