coderClaw

ClawHub

ClawHub is the public skill registry for CoderClaw. 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.

💡 Multiple registries. CoderClaw is designed to be agnostic: the default endpoint is ClawHub (https://clawhub.ai), but you can point at any compatible service (for example an OpenClaw deployment) by setting skills.registry.url in your configuration. The CLI hint shown by coderclaw skills will also adjust based on the skills.registry.cli string (defaults to npx clawhub).

Site: clawhub.ai

What ClawHub is

How it works

  1. A user publishes a skill bundle (files + metadata).
  2. ClawHub stores the bundle, parses metadata, and assigns a version.
  3. The registry indexes the skill for search and discovery.
  4. Users browse, download, and install skills in CoderClaw.

What you can do

Who this is for (beginner-friendly)

If you want to add new capabilities to your CoderClaw agent, ClawHub is the easiest way to find and install skills. You do not need to know how the backend works. You can:

Quick start (non-technical)

  1. Install the CLI (see next section).
  2. Search for something you need:
    • clawhub search "calendar"
  3. Install a skill:
    • clawhub install <skill-slug>
  4. Start a new CoderClaw session so it picks up the new skill.

Install the CLI

Pick one:

npm i -g clawhub
pnpm add -g clawhub

How it fits into CoderClaw

By default, the CLI installs skills into ./skills under your current working directory. If a CoderClaw workspace is configured, clawhub falls back to that workspace unless you override --workdir (or CLAWHUB_WORKDIR). CoderClaw loads workspace skills from <workspace>/skills and will pick them up in the next session. If you already use ~/.coderclaw/skills or bundled skills, workspace skills take precedence.

For more detail on how skills are loaded, shared, and gated, see Skills.

Skill system overview

A skill is a versioned bundle of files that teaches CoderClaw how to perform a specific task. Each publish creates a new version, and the registry keeps a history of versions so users can audit changes.

A typical skill includes:

ClawHub uses metadata to power discovery and safely expose skill capabilities. The registry also tracks usage signals (such as stars and downloads) to improve ranking and visibility.

What the service provides (features)

Security and moderation

ClawHub is open by default. Anyone can upload skills, but a GitHub account must be at least one week old to publish. This helps slow down abuse without blocking legitimate contributors.

Reporting and moderation:

Interested in becoming a moderator? Ask in the CoderClaw Discord and contact a moderator or maintainer.

CLI commands and parameters

Global options (apply to all commands):

Auth:

Options:

Search:

Install:

Update:

List:

Publish:

Delete/undelete (owner/admin only):

Sync (scan local skills + publish new/updated):

Common workflows for agents

Search for skills

clawhub search "postgres backups"

Download new skills

clawhub install my-skill-pack

Update installed skills

clawhub update --all

Back up your skills (publish or sync)

For a single skill folder:

clawhub publish ./my-skill --slug my-skill --name "My Skill" --version 1.0.0 --tags latest

To scan and back up many skills at once:

clawhub sync --all

Advanced details (technical)

Versioning and tags

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

clawhub sync scans your current workdir first. If no skills are found, it falls back to known legacy locations (for example ~/coderclaw/skills and ~/.coderclaw/skills). This is designed to find older skill installs without extra flags.

Storage and lockfile

Telemetry (install counts)

When you run clawhub sync while logged in, the CLI sends a minimal snapshot to compute install counts. You can disable this entirely:

export CLAWHUB_DISABLE_TELEMETRY=1

Environment variables