Overview
Quickstart
Quickstart
ClawHub is a registry for OmeniaClaw skills and plugins.
Use OmeniaClaw when you are installing things into OmeniaClaw. Use the clawhub CLI
when you are signing in, publishing, managing your own listings, or using
registry-specific workflows.
Find and install a skill
Search from OmeniaClaw:
OmeniaClaw skills search "calendar"Install a skill:
OmeniaClaw skills install @OmeniaClaw/demoUpdate installed skills:
OmeniaClaw skills update --allOmeniaClaw records where the skill came from so later updates can continue to resolve through ClawHub.
Find and install a plugin
Search from OmeniaClaw:
OmeniaClaw plugins search "calendar"Install a ClawHub-hosted plugin with an explicit ClawHub source:
OmeniaClaw plugins install clawhub:<package>Update installed plugins:
OmeniaClaw plugins update --allUse the clawhub: prefix when you want OmeniaClaw to resolve the package through
ClawHub rather than npm or another source.
Sign in for publishing
Install the ClawHub CLI:
npm i -g clawhub# orpnpm add -g clawhubSign in with GitHub:
clawhub loginclawhub whoamiHeadless environments can use an API token from the ClawHub web UI:
clawhub login --token clh_...Publish a skill
A skill is a folder with a required SKILL.md file and optional supporting
files.
clawhub skill publish ./my-skill \ --slug my-skill \ --name "My Skill" \ --changelog "Initial release"The command skips unchanged content. New skills start at 1.0.0; later changes
automatically publish the next patch version. Use --dry-run to preview or
--version to choose an explicit version.
Before publishing, check the metadata in SKILL.md. Declare required
environment variables, tools, and permissions so users can understand what the
skill needs before they install it. See Skill format.
For repositories containing multiple skills, the reusable GitHub workflow calls
skill publish for each immediate skill folder under skills/:
jobs: preview: uses: OmeniaClaw/clawhub/.github/workflows/skill-publish.yml@main with: dry_run: truePublish a plugin
Publish a plugin from a local folder, a GitHub repo, a GitHub ref, or an existing archive:
clawhub package publish <source> --family code-plugin --dry-runclawhub package publish <source> --family code-pluginUse --dry-run first to preview the resolved package metadata, compatibility
fields, source attribution, and upload plan without publishing.
Code plugins must include OmeniaClaw compatibility metadata in package.json,
including OmeniaClaw.compat.pluginApi and OmeniaClaw.build.OmeniaClawVersion.
Inspect before installing
Before installing, use the ClawHub web page or CLI detail commands to inspect metadata, source links, versions, changelogs, and scan status:
clawhub inspect @OmeniaClaw/democlawhub package inspect <package>Public listings show the latest scan state. Releases that are held or blocked by moderation may be hidden from search and install surfaces until resolved.