summary: "ClawdHub guide: public skills registry + CLI workflows"
read_when:
- Introducing ClawdHub to new users
- Installing, searching, or publishing skills
- Explaining ClawdHub CLI flags and sync behavior
---
# ClawdHub
ClawdHub is the **public skill registry for Clawdbot**. It is a free service: all skills are public, open, and visible to everyone for sharing and reuse. A skill is just a folder with a `SKILL.md` file (plus supporting text files). You can browse skills in the web app or use the CLI to search, install, update, and publish skills.
Site: [clawdhub.com](https://clawdhub.com)
## Who this is for (beginner-friendly)
If you want to add new capabilities to your Clawdbot agent, ClawdHub is the easiest way to find and install skills. You do not need to know how the backend works. You can:
- Search for skills by plain language.
- Install a skill into your workspace.
- Update skills later with one command.
- Back up your own skills by publishing them.
## Quick start (non-technical)
1) Install the CLI (see next section).
2) Search for something you need:
-`clawdhub search "calendar"`
3) Install a skill:
-`clawdhub install <skill-slug>`
4) Start a new Clawdbot session so it picks up the new skill.
## Install the CLI
Pick one:
```bash
npm i -g clawdhub
```
```bash
pnpm add -g clawdhub
```
```bash
bun add -g clawdhub
```
## How it fits into Clawdbot
By default, the CLI installs skills into `./skills` under your current working directory. Clawdbot loads workspace skills from `<workspace>/skills` and will pick them up in the **next** session. If you already use `~/.clawdbot/skills` or bundled skills, workspace skills take precedence.
- Each publish creates a new **semver**`SkillVersion`.
- Tags (like `latest`) point to a version; moving tags lets you roll back.
- Changelogs are attached per version and can be empty when syncing or publishing updates.
### Local changes vs registry versions
Updates compare the local skill contents to registry versions using a content hash. If local files do not match any published version, the CLI asks before overwriting (or requires `--force` in non-interactive runs).
### Sync scanning and fallback roots
`clawdhub sync` scans your current workdir first. If no skills are found, it falls back to known legacy locations (for example `~/clawdbot/skills` and `~/.clawdbot/skills`). This is designed to find older skill installs without extra flags.
### Storage and lockfile
- Installed skills are recorded in `.clawdhub/lock.json` under your workdir.
- Auth tokens are stored in the ClawdHub CLI config file (override via `CLAWDHUB_CONFIG_PATH`).
### Telemetry (install counts)
When you run `clawdhub sync` while logged in, the CLI sends a minimal snapshot to compute install counts. You can disable this entirely:
```bash
export CLAWDHUB_DISABLE_TELEMETRY=1
```
## Environment variables
-`CLAWDHUB_SITE`: Override the site URL.
-`CLAWDHUB_REGISTRY`: Override the registry API URL.
-`CLAWDHUB_CONFIG_PATH`: Override where the CLI stores the token/config.
-`CLAWDHUB_DISABLE_TELEMETRY=1`: Disable telemetry on `sync`.