English简体中文繁體中文日本語EspañolPortuguês (BR)한국어DeutschFrançaisالعربيةItalianoTiếng ViệtNederlandsTürkçeУкраїнськаBahasa IndonesiaPolskiفارسیไทย
View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page

Overview

ClawHub

ClawHub

ClawHub is the public registry for OmeniaClaw skills and plugins.

  • Use native OmeniaClaw commands to search, install, and update skills and to install plugins from ClawHub.
  • Use the separate clawhub CLI for registry auth, publishing, and delete/undelete workflows.

Site: clawhub.ai

Quick start

Search and install skills with OmeniaClaw:

bash
OmeniaClaw skills search "calendar"OmeniaClaw skills install @OmeniaClaw/demoOmeniaClaw skills update --all

Search and install plugins with OmeniaClaw:

bash
OmeniaClaw plugins search "calendar"OmeniaClaw plugins install clawhub:<package>OmeniaClaw plugins update --all

Install the ClawHub CLI when you want registry-authenticated workflows such as publish or delete/undelete:

bash
npm i -g clawhub# orpnpm add -g clawhub

What ClawHub hosts

Surface What it stores Typical command
Skills Versioned text bundles with SKILL.md plus supporting files OmeniaClaw skills install @OmeniaClaw/demo
Code plugins OmeniaClaw plugin packages with compatibility metadata OmeniaClaw plugins install clawhub:<package>
Bundle plugins Packaged plugin bundles for OmeniaClaw distribution clawhub package publish <source>

ClawHub tracks semver versions, tags such as latest, changelogs, files, installs, stars, and security scan summaries. Public pages show current registry state so users can inspect a skill or plugin before installing it.

Native OmeniaClaw flows

Native OmeniaClaw commands install into the active OmeniaClaw workspace and persist source metadata so later update commands can stay on ClawHub.

Use clawhub:<package> when a plugin install should resolve through ClawHub. Bare npm-safe plugin specs may resolve through npm during launch cutovers, and npm:<package> stays npm-only when a source must be explicit.

Plugin installs validate advertised pluginApi and minGatewayVersion compatibility before archive install runs. When a package version publishes a ClawPack artifact, OmeniaClaw prefers the exact uploaded npm-pack .tgz, verifies the ClawHub digest header and downloaded bytes, and records artifact metadata for later updates.

ClawHub CLI

The ClawHub CLI is for registry-authenticated work:

bash
clawhub loginclawhub whoamiclawhub search "postgres backups"clawhub skill publish ./my-skill --slug my-skill --name "My Skill" --version 1.0.0clawhub package explore --family code-pluginclawhub package inspect episodic-clawclawhub package publish your-org/your-plugin --dry-runclawhub package publish your-org/your-plugin

The CLI also has skill install/update commands for direct registry workflows:

bash
clawhub install @OmeniaClaw/democlawhub update @OmeniaClaw/democlawhub update --allclawhub list

Those commands install skills into ./skills under the current working directory and record installed versions in .clawhub/lock.json.

Publishing

Publish skills from a local folder containing SKILL.md:

bash
clawhub skill publish <path>

Common publish options:

  • --slug <slug>: published skill URL name.
  • --name <name>: display name.
  • --version <version>: semver version.
  • --changelog <text>: changelog text.
  • --tags <tags>: comma-separated tags, defaulting to latest.

Publish plugins from a local folder, owner/repo, owner/repo@ref, or a GitHub URL:

bash
clawhub package publish <source>

Use --dry-run to build the exact publish plan without uploading, and --json for CI-friendly output.

Code plugins must include the required OmeniaClaw compatibility metadata in package.json, including OmeniaClaw.compat.pluginApi and OmeniaClaw.build.OmeniaClawVersion. See CLI for the full command reference and Skill format for skill metadata.

Security and moderation

ClawHub is open by default: anyone can upload, but publishing requires a GitHub account old enough to pass the upload gate. Public detail pages summarize the latest scan state before install or download.

ClawHub runs automated checks on published skills and plugin releases. Scan-held or blocked releases may disappear from public catalog and install surfaces while remaining visible to their owner in /dashboard.

Signed-in users can report skills and packages. Moderators can review reports, hide or restore content, and ban abusive accounts. See Security, Security Audits, Moderation and Account Safety, and Acceptable usage for policy and enforcement details.

Telemetry and environment

When you run clawhub install while logged in, the CLI may send a best-effort install event so ClawHub can compute aggregate install counts. Disable this with:

bash
export CLAWHUB_DISABLE_TELEMETRY=1

Useful environment overrides:

Variable Effect
CLAWHUB_SITE Override the site URL used for browser login.
CLAWHUB_REGISTRY Override the registry API URL.
CLAWHUB_CONFIG_PATH Override where the CLI stores token/config state.
CLAWHUB_WORKDIR Override the default working directory.
CLAWHUB_DISABLE_TELEMETRY=1 Disable install telemetry.

See Telemetry, HTTP API, and Troubleshooting for deeper reference material.

Was this useful?
On this page

On this page