Clawdhub

What It Does

Think of it as npm, but purpose-built for agent capabilities.

ClawdHub is the package manager for AI agent skills. It lets your agent search the clawdhub.com registry, install skills on the fly, keep installed skills in sync with the latest versions, and publish new or updated skills — all via the `clawdhub` CLI.

Key Features

• Skill Search — Query the clawdhub.com registry with a plain-language search string (e.g., `clawdhub search "postgres backups"`) and get back matching skills. Lets an agent or developer discover relevant capabilities without leaving the terminal.
• Install & Version Pinning — Install any skill by slug with `clawdhub install my-skill`, or pin to an exact release with `--version 1.2.3`. Skills land in `./skills` by default, keeping your workspace organized.
• Hash-Based Update Detection — The `update` command hashes local skill files, resolves the matching upstream version, and upgrades to the latest — or to a specific version with `--version`. Run `clawdhub update --all` to sync every installed skill in one pass, with `--no-input --force` for unattended automation.
• Skill Publishing — Package and publish a local skill folder to the registry with a single `clawdhub publish` command, supplying slug, name, version, and changelog inline. Authentication is handled via `clawdhub login`.
• Configurable Registry & Workdir — Override the default registry (`https://clawdhub.com`) via the `CLAWDHUB_REGISTRY` environment variable or `--registry` flag. The working directory and install destination are equally configurable with `--workdir` and `--dir`.

Use Cases

• On-the-fly skill acquisition during an agent session — An agent realizes mid-task that it needs a capability it doesn't have. It calls ClawdHub to search the registry, installs the relevant skill on the spot, and continues without interrupting the workflow.
• Automated skill updates in CI/CD — A CI pipeline runs `clawdhub update --all --no-input --force` on each build to ensure the deployed agent always ships with the latest skill versions, with no human prompts required.
• Publishing a new or updated skill — A skill author runs `clawdhub publish ./my-skill --slug my-skill --name "My Skill" --version 1.2.0 --changelog "Fixes + docs"` to release their work to the clawdhub.com marketplace immediately after development.
• Auditing installed skills in a workspace — A developer runs `clawdhub list` to get a snapshot of every skill currently installed, their versions, and their locations — useful for debugging or preparing a reproducible environment.