clawhub

• Fetching new skills at runtime — your agent needs a capability it wasn't originally packaged with and should pull it from the registry on demand.
• Version-pinning installed skills — you want to lock a skill to a known-good version (e.g. 1.2.3) to avoid unexpected breaking changes.
• Keeping a workspace up to date — you want to bulk-upgrade all installed skills to their latest releases with a single update --all command.
• Publishing your own skills — you've built a new skill folder and want to share it on clawhub.com with a versioned release and changelog.

• If you only need a one-time skill installation during initial setup — a direct file copy or a standard npm install step may be simpler than invoking the full ClawHub CLI.
• If your environment has no internet access — ClawHub relies on the clawhub.com registry (or a custom CLAWHUB_REGISTRY) and will not function in fully air-gapped environments without a self-hosted registry.

Query the clawhub.com registry with natural-language or keyword searches (e.g. clawhub search "postgres backups") to discover available skills without leaving your terminal or agent session.

Install any skill by slug with clawhub install my-skill, or pin to a specific release with --version 1.2.3. Skills land in ./skills by default, configurable via --dir or CLAWHUB_WORKDIR.

The update command hashes local skill files, resolves the matching upstream version, and upgrades to the latest release (or a pinned version). Use --all to upgrade every installed skill at once, with --force and --no-input flags for automated pipelines.

Publish a local skill folder to the registry with a single command, supplying a slug, display name, version, and changelog string. Requires a clawhub login session.

Override the default https://clawhub.com registry via the CLAWHUB_REGISTRY env var or --registry flag. Working directory defaults to the current directory (falling back to the OpenClaw workspace) and can be overridden with --workdir or CLAWHUB_WORKDIR.

An agent discovers mid-task that it needs a skill not yet installed. It calls clawhub install <slug> to pull the latest version from the registry and immediately gains the capability — no human intervention required.

A deployment pipeline runs clawhub update --all --no-input --force to ensure every skill in the workspace is at its latest release before the agent environment starts, eliminating version drift across deployments.

A developer finishes a skill update, runs clawhub publish ./my-skill --slug my-skill --version 1.3.0 --changelog "Bug fixes + new actions" and the skill is immediately available on clawhub.com for other users and agents to install.

A team pins critical skills to tested versions using clawhub install my-skill --version 1.2.3, ensuring production agents never auto-upgrade to an untested release without an explicit version bump in their configuration.