home / skills / openclaw / openclaw / clawdhub

clawdhub skill

/skills/clawdhub

This skill helps you manage clawdhub CLI operations to search, install, update, and publish skills from clawdhub.com efficiently.

npx playbooks add skill openclaw/openclaw --skill clawdhub

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.4 KB
---
name: clawdhub
description: Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawdhub CLI.
metadata: {"openclaw":{"requires":{"bins":["clawdhub"]},"install":[{"id":"node","kind":"node","package":"clawdhub","bins":["clawdhub"],"label":"Install ClawdHub CLI (npm)"}]}}
---

# ClawdHub CLI

Install
```bash
npm i -g clawdhub
```

Auth (publish)
```bash
clawdhub login
clawdhub whoami
```

Search
```bash
clawdhub search "postgres backups"
```

Install
```bash
clawdhub install my-skill
clawdhub install my-skill --version 1.2.3
```

Update (hash-based match + upgrade)
```bash
clawdhub update my-skill
clawdhub update my-skill --version 1.2.3
clawdhub update --all
clawdhub update my-skill --force
clawdhub update --all --no-input --force
```

List
```bash
clawdhub list
```

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

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

Overview

This skill integrates the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. It lets you fetch new skills on the fly, sync installed skills to a specific version or the latest release, and publish local skill folders using the npm-installed clawdhub tool. Ideal for managing a personal assistant skill library across platforms.

How this skill works

The skill wraps the ClawdHub CLI commands: search to find skills, install to add them to your workspace, update to reconcile local changes and upgrade versions, list to show installed skills, and publish to push a local skill to ClawdHub. It respects environment variables and CLI flags for registry, workdir, versions, and force/no-input behaviors. Updates perform a hash-based match of local files and then resolve and apply the requested version.

When to use it

  • You need to discover and add third-party agent skills quickly.
  • You want to upgrade installed skills to the latest or a specific version.
  • You maintain local skill folders and want to publish or update them on ClawdHub.
  • You run CI/CD that should sync skill directories automatically.
  • You need to change the registry or workspace location for installs.

Best practices

  • Install the CLI globally with npm (npm i -g clawdhub) to access commands anywhere.
  • Authenticate before publishing using clawdhub login and confirm with clawdhub whoami.
  • Use explicit --version when reproducible installs or rollbacks are required.
  • Run clawdhub update --all in a controlled environment or CI, and use --no-input for noninteractive upgrades.
  • Override defaults via CLAWDHUB_REGISTRY and CLAWDHUB_WORKDIR for multi-environment workflows.

Example use cases

  • Search for a skill that manages Postgres backups: clawdhub search "postgres backups".
  • Install a specific skill version into your workspace: clawdhub install my-skill --version 1.2.3.
  • Force an upgrade after local changes: clawdhub update my-skill --force.
  • Publish a new local skill folder with metadata: clawdhub publish ./my-skill --slug my-skill --name "My Skill" --version 1.2.0 --changelog "Fixes + docs".
  • Batch update all installed skills in CI: clawdhub update --all --no-input --force.

FAQ

How do I change the registry or install location?

Set the CLAWDHUB_REGISTRY or CLAWDHUB_WORKDIR environment variables, or use --registry and --workdir/--dir flags to override defaults.

What does the update command do with local modifications?

Update hashes local files to detect matches, then resolves a matching version and upgrades; use --force to override or --version to pin a specific release.