playbooks

home / skills / openclaw / skills / clawdhub-copy

clawdhub-copy skill

/skills/jk50505k/clawdhub-copy

This skill helps you discover, install, update, and publish AI-powered agents from ClawdHub, keeping skills current and accessible.

npx playbooks add skill openclaw/skills --skill clawdhub-copy

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

Files (2)
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: {"clawdbot":{"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 Clawdbot 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 provides a CLI wrapper for interacting with ClawdHub to search, install, update, list, and publish agent skills. It makes it easy to fetch archived skill versions, keep local skills in sync with the registry, and publish new or updated skill folders using the npm-installed clawdhub CLI. Designed for fast on-the-fly skill management and reproducible deployments.

How this skill works

The CLI talks to the default ClawdHub registry (https://clawdhub.com) but can target a custom registry via environment variables or flags. It can search the archive, install a specific skill or version into a configurable workdir, compute file hashes to detect local matches, and update to matched or latest versions. Publishing requires authentication and uploads a local skill directory with metadata like slug, name, version, and changelog.

When to use it

  • You need to fetch a skill quickly from the ClawdHub archive into your workspace.
  • You want to pin a skill to a specific version for reproducible runs.
  • You must sync local skills to the latest registry versions across a project.
  • You are preparing to publish a new or updated skill to ClawdHub.
  • You need to audit or list all installed skills and their versions.

Best practices

  • Install via npm globally (npm i -g clawdhub) to access the CLI system-wide.
  • Use version pins when reproducibility is required, otherwise allow updates to latest.
  • Set CLAWDHUB_WORKDIR or use --workdir to centralize skill installs for team projects.
  • Run clawdhub login before publishing and verify identity with clawdhub whoami.
  • Use --no-input and --force in automation scripts to avoid interactive prompts.

Example use cases

  • Search the archive for a backup skill: find relevant tools without browsing the site.
  • Install a named skill into ./skills for local development or CI testing.
  • Update all installed skills in a workspace before a release with clawdhub update --all.
  • Publish a prepared skill folder to the registry with metadata and a changelog.
  • Force-upgrade a skill when local files match an older archived hash.

FAQ

How do I change the registry or install directory?

Override defaults with CLAWDHUB_REGISTRY or CLAWDHUB_WORKDIR environment variables, or pass --registry and --workdir/--dir flags.

What does the update command use to match local files?

Update hashes local files to resolve a matching archived version and then upgrades to the latest unless you specify --version.

How do I publish a skill?

Authenticate with clawdhub login, then run clawdhub publish pointing at your skill folder and include slug, name, version, and changelog.