ClawHub

What this skill does

• •Search registry for pre-built agent skills
• •Install and manage third-party skill modules locally
• •Perform version-controlled updates with hash-based validation
• •Publish custom skills to the central registry
• •Override default registries and storage paths via configuration

When to use it

• ✓Expanding your OpenClaw assistant with community-developed tools
• ✓Standardizing agent skill versions across multiple local projects
• ✓Distributing your custom AI tools to other OpenClaw users
• ✓Maintaining local skill integrity using automated update checks

When not to use it

• ✕Managing general software packages not related to the OpenClaw ecosystem
• ✕Deploying large-scale production microservices
• ✕Installing dependencies for non-agent JavaScript projects

How to invoke it

Example prompts that trigger this skill:

• “clawhub search for postgres backup tools”
• “clawhub install the latest weather data skill”
• “update all my currently installed skills”
• “publish this folder as a new agent skill”
• “list everything currently installed in my workspace”

Example workflow

1. Run 'clawhub search' to find a relevant skill slug
2. Execute 'clawhub install [skill-name]' to pull it into your ./skills directory
3. Configure local environment variables if the skill requires authentication
4. Periodically run 'clawhub update --all' to ensure your features are current
5. Verify the installation status using 'clawhub list'

Prerequisites

• –Node.js runtime installed
• –OpenClaw environment initialized

Pitfalls & limitations

• !Requires active network connectivity to reach the default registry
• !Local skill directory structure must align with OpenClaw conventions
• !Security caution: skills run shell commands; verify source before installation

FAQ

How it compares

Unlike manual cloning or npm installs, ClawHub manages the specific lifecycle, versioning, and registry metadata required for agent-based behaviors in the OpenClaw architecture.

Source & trust

From the source: “# ClawHub CLI Install ```bash npm i -g clawhub ``` Auth (publish) ```bash clawhub login clawhub whoami ``` Search ```bash clawhub search "postgres backups" ``` Install ```bash clawhub install my-skill clawhub install my-skill --version 1.2.3 ``` Update (hash-based match + upgrade) ```bash clawhub up…”

# ClawHub CLI

Install

```bash
npm i -g clawhub
```

Auth (publish)

```bash
clawhub login
clawhub whoami
```

Search

```bash
clawhub search "postgres backups"
```

Install

```bash
clawhub install my-skill
clawhub install my-skill --version 1.2.3
```

Update (hash-based match + upgrade)

```bash
clawhub update my-skill
clawhub update my-skill --version 1.2.3
clawhub update --all
clawhub update my-skill --force
clawhub update --all --no-input --force
```

List

```bash
clawhub list
```

Publish

```bash
clawhub publish ./my-skill --slug my-skill --name "My Skill" --version 1.2.0 --changelog "Fixes + docs"
```

Notes

- Default registry: https://clawhub.com (override with CLAWHUB_REGISTRY or --registry)
- Default workdir: cwd (falls back to OpenClaw workspace); install dir: ./skills (override with --workdir / --dir / CLAWHUB_WORKDIR)
- Update command hashes local files, resolves matching version, and upgrades to latest unless --version is set

Quoted from openclaw/openclaw for reference — see the original for the authoritative, latest version.

Recommended Rules

Recommended Workflows

Recommended MCP Servers