ClawHub

ClawHub is the public registry for Velaclaw skills and plugins.

Use native velaclaw commands to search/install/update skills and install plugins from ClawHub.
Use the separate clawhub CLI when you need registry auth, publish, delete, undelete, or sync workflows.

Native Velaclaw flows

Skills:

velaclaw skills search "calendar"
velaclaw skills install <skill-slug>
velaclaw skills update --all

Plugins:

velaclaw plugins install clawhub:<package>
velaclaw plugins update --all

Bare npm-safe plugin specs are also tried against ClawHub before npm:

velaclaw plugins install velaclaw-codex-app-server

Native velaclaw commands install into your active workspace and persist source metadata so later update calls can stay on ClawHub. Plugin installs validate advertised pluginApi and minGatewayVersion compatibility before archive install runs, so incompatible hosts fail closed early instead of partially installing the package. velaclaw plugins install clawhub:... only accepts installable plugin families. If a ClawHub package is actually a skill, Velaclaw stops and points you at velaclaw skills install <slug> instead.

Team shared asset bridge

Team control planes can expose ClawHub skills through the same shared asset server used for shared-skills. This lets members discover and activate ClawHub skills on demand without receiving the ClawHub token. Enable it on the control plane process:

VELACLAW_TEAM_CLAWHUB_SKILLS_ENABLED=1
VELACLAW_CLAWHUB_TOKEN=clh_...

Behavior:

The team asset manifest includes a ClawHub Skill Hub shared skill.
/asset-server/resolve searches ClawHub and returns matching skills as kind: "skills" assets.
/asset-server/items/:id downloads the matching skill bundle on the control plane and returns text files to the member injector.
The member injector materializes those files under skills/team-shared-active-<skill>/.
The token remains control-plane-only; member runtimes receive materialized files, not registry credentials.

Optional limits:

VELACLAW_TEAM_CLAWHUB_SKILLS_SEARCH_LIMIT=4
VELACLAW_TEAM_CLAWHUB_SKILLS_FILE_LIMIT=160
VELACLAW_TEAM_CLAWHUB_SKILLS_FILE_MAX_BYTES=262144
VELACLAW_TEAM_CLAWHUB_SKILLS_TOTAL_MAX_BYTES=1048576

What ClawHub is

A public registry for Velaclaw skills and plugins.
A versioned store of skill bundles and metadata.
A discovery surface for search, tags, and usage signals.

How it works

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

What you can do

Publish new skills and new versions of existing skills.
Discover skills by name, tags, or search.
Download skill bundles and inspect their files.
Report skills that are abusive or unsafe.
If you are a moderator, hide, unhide, delete, or ban.

Who this is for (beginner-friendly)

If you want to add new capabilities to your Velaclaw agent, ClawHub 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)

Search for something you need:
- velaclaw skills search "calendar"
Install a skill:
- velaclaw skills install <skill-slug>
Start a new Velaclaw session so it picks up the new skill.
If you want to publish or manage registry auth, install the separate clawhub CLI too.

Install the ClawHub CLI

You only need this for registry-authenticated workflows such as publish/sync:

npm i -g clawhub

pnpm add -g clawhub

How it fits into Velaclaw

Native velaclaw skills install installs into the active workspace skills/ directory. velaclaw plugins install clawhub:... records a normal managed plugin install plus ClawHub source metadata for updates. Anonymous ClawHub plugin installs also fail closed for private packages. Community or other non-official channels can still install, but Velaclaw warns so operators can review source and verification before enabling them. The separate clawhub CLI also installs skills into ./skills under your current working directory. If an Velaclaw workspace is configured, clawhub falls back to that workspace unless you override --workdir (or CLAWHUB_WORKDIR). Velaclaw loads workspace skills from <workspace>/skills and will pick them up in the next session. If you already use ~/.velaclaw/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 Velaclaw 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:

A SKILL.md file with the primary description and usage.
Optional configs, scripts, or supporting files used by the skill.
Metadata such as tags, summary, and install requirements.

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)

Public browsing of skills and their SKILL.md content.
Search powered by embeddings (vector search), not just keywords.
Versioning with semver, changelogs, and tags (including latest).
Downloads as a zip per version.
Stars and comments for community feedback.
Moderation hooks for approvals and audits.
CLI-friendly API for automation and scripting.

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:

Any signed in user can report a skill.
Report reasons are required and recorded.
Each user can have up to 20 active reports at a time.
Skills with more than 3 unique reports are auto hidden by default.
Moderators can view hidden skills, unhide them, delete them, or ban users.
Abusing the report feature can result in account bans.

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

CLI commands and parameters

Global options (apply to all commands):

--workdir <dir>: Working directory (default: current dir; falls back to Velaclaw workspace).
--dir <dir>: Skills directory, relative to workdir (default: skills).
--site <url>: Site base URL (browser login).
--registry <url>: Registry API base URL.
--no-input: Disable prompts (non-interactive).
-V, --cli-version: Print CLI version.

Auth:

clawhub login (browser flow) or clawhub login --token <token>
clawhub logout
clawhub whoami

Options:

--token <token>: Paste an API token.
--label <label>: Label stored for browser login tokens (default: CLI token).
--no-browser: Do not open a browser (requires --token).

Search:

clawhub search "query"
--limit <n>: Max results.

Install:

clawhub install <slug>
--version <version>: Install a specific version.
--force: Overwrite if the folder already exists.

Update:

clawhub update <slug>
clawhub update --all
--version <version>: Update to a specific version (single slug only).
--force: Overwrite when local files do not match any published version.

List:

clawhub list (reads .clawhub/lock.json)

Publish skills:

clawhub skill publish <path>
--slug <slug>: Skill slug.
--name <name>: Display name.
--version <version>: Semver version.
--changelog <text>: Changelog text (can be empty).
--tags <tags>: Comma-separated tags (default: latest).

Publish plugins:

clawhub package publish <source>
<source> can be a local folder, owner/repo, owner/repo@ref, or a GitHub URL.
--dry-run: Build the exact publish plan without uploading anything.
--json: Emit machine-readable output for CI.
--source-repo, --source-commit, --source-ref: Optional overrides when auto-detection is not enough.

Delete/undelete (owner/admin only):

clawhub delete <slug> --yes
clawhub undelete <slug> --yes

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

clawhub sync
--root <dir...>: Extra scan roots.
--all: Upload everything without prompts.
--dry-run: Show what would be uploaded.
--bump <type>: patch|minor|major for updates (default: patch).
--changelog <text>: Changelog for non-interactive updates.
--tags <tags>: Comma-separated tags (default: latest).
--concurrency <n>: Registry checks (default: 4).

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 skill 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

Publish a plugin from GitHub

clawhub package publish your-org/your-plugin --dry-run
clawhub package publish your-org/your-plugin
clawhub package publish your-org/your-plugin@v1.0.0
clawhub package publish https://github.com/your-org/your-plugin

Code plugins must include the required Velaclaw metadata in package.json:

{
  "name": "@myorg/velaclaw-my-plugin",
  "version": "1.0.0",
  "type": "module",
  "velaclaw": {
    "extensions": ["./index.ts"],
    "compat": {
      "pluginApi": ">=2026.3.24-beta.2",
      "minGatewayVersion": "2026.3.24-beta.2"
    },
    "build": {
      "velaclawVersion": "2026.3.24-beta.2",
      "pluginSdkVersion": "2026.3.24-beta.2"
    }
  }
}

Advanced details (technical)

Versioning and tags

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

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

Storage and lockfile

Installed skills are recorded in .clawhub/lock.json under your workdir.
Auth tokens are stored in the ClawHub CLI config file (override via CLAWHUB_CONFIG_PATH).

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

CLAWHUB_SITE: Override the site URL.
CLAWHUB_REGISTRY: Override the registry API URL.
CLAWHUB_CONFIG_PATH: Override where the CLI stores the token/config.
CLAWHUB_WORKDIR: Override the default workdir.
CLAWHUB_DISABLE_TELEMETRY=1: Disable telemetry on sync.

Overview

Plugins

Skills

Automation & Tasks

Tools

Agent coordination

ClawHub

ClawHub

Native Velaclaw flows

Team shared asset bridge

What ClawHub is

How it works

What you can do

Who this is for (beginner-friendly)

Quick start (non-technical)

Install the ClawHub CLI

How it fits into Velaclaw

Skill system overview

What the service provides (features)

Security and moderation

CLI commands and parameters

Common workflows for agents

Search for skills

Download new skills

Update installed skills

Back up your skills (publish or sync)

Publish a plugin from GitHub

Advanced details (technical)

Versioning and tags

Local changes vs registry versions

Sync scanning and fallback roots

Storage and lockfile

Telemetry (install counts)

Environment variables

​ClawHub

​Native Velaclaw flows

​Team shared asset bridge

​What ClawHub is

​How it works

​What you can do

​Who this is for (beginner-friendly)

​Quick start (non-technical)

​Install the ClawHub CLI

​How it fits into Velaclaw

​Skill system overview

​What the service provides (features)

​Security and moderation

​CLI commands and parameters

​Common workflows for agents

​Search for skills

​Download new skills

​Update installed skills

​Back up your skills (publish or sync)

​Publish a plugin from GitHub

​Advanced details (technical)

​Versioning and tags

​Local changes vs registry versions

​Sync scanning and fallback roots

​Storage and lockfile

​Telemetry (install counts)

​Environment variables

ClawHub

Native Velaclaw flows

Team shared asset bridge

What ClawHub is

How it works

What you can do

Who this is for (beginner-friendly)

Quick start (non-technical)

Install the ClawHub CLI

How it fits into Velaclaw

Skill system overview

What the service provides (features)

Security and moderation

CLI commands and parameters

Common workflows for agents

Search for skills

Download new skills

Update installed skills

Back up your skills (publish or sync)

Publish a plugin from GitHub

Advanced details (technical)

Versioning and tags

Local changes vs registry versions

Sync scanning and fallback roots

Storage and lockfile

Telemetry (install counts)

Environment variables