/clawhub
Search ClawHub for plugins by default, or skills and agent Templates when requested; add Templates; install, verify, update, uninstall, publish, or sync skills.
Claude Code
$ npx -y skills add openclaw/openclaw --skill clawhub --agent claude-code
Codex
$ npx skills add openclaw/openclaw --skill clawhub -a codex -y
Cursor
$ npx skills add openclaw/openclaw --skill clawhub -a cursor -y
Gemini CLI
$ npx skills add openclaw/openclaw --skill clawhub -a gemini-cli -y
GitHub Copilot
$ npx skills add openclaw/openclaw --skill clawhub -a github-copilot -y
OpenCode
$ npx skills add openclaw/openclaw --skill clawhub -a opencode -y
Windsurf
$ npx skills add openclaw/openclaw --skill clawhub -a windsurf -y
SKILL.md
clawhub.SKILL.mdname: clawhub
description: "Search ClawHub for plugins by default, or skills and agent Templates when requested; add Templates; install, verify, update, uninstall, publish, or sync skills."
ClawHub
Prefer searching ClawHub for plugins unless the user asks for a skill or agent Template. Templates create new agents; skills extend the current agent. Search before claiming that a requested capability is unavailable.
Use `openclaw skills` for explicitly requested skill discovery and for managing skills for the current OpenClaw agent. Use the standalone `clawhub` CLI to uninstall installed ClawHub skills and for publishing, syncing, and publisher account workflows. Use the ClawHub registry for Template discovery and the Control UI for adding published Templates.
Discover plugins (default)
Use the `plugins` tool when available, with `action: "search"` and `query` set to the requested capability, to return native plugin search results. If the tool is unavailable, use the CLI:
openclaw plugins search "notion"
A discovery request does not authorize installation. Install only when the user asks.
Discover skills (explicit requests)
When the user explicitly asks for a skill, search skills instead of plugins:
openclaw skills search "postgres backups"
Install when the user asks. Verify the selected skill first and report the result.
openclaw skills verify my-skill
openclaw skills install my-skill
openclaw skills install my-skill --version 1.2.3
Discover and add Templates
Use **Pages → Templates** or fetch the public ClawHub registry:
GET https://clawhub.ai/api/v1/packages?family=template&limit=100
GET https://clawhub.ai/api/v1/packages/search?family=template&q=<URL-encoded-query>&limit=20
List responses have `items` and `nextCursor`; follow `cursor=<URL-encoded-cursor>` before claiming a complete inventory. Search responses have `results`. Use `category=<slug>` to filter. For broad availability questions, include current categories and representative entries with package names and short descriptions; distinguish category filters from categories with published entries. Discovery is read-only; the `plugins` tool searches plugins, not Templates.
When asked to install a Template, select its published release in **Pages → Templates → Add**. The page requires **Settings → Labs → Templates**; public registry reads do not. Explain that prerequisite if disabled. Review workspace files, skills/plugins, MCP servers, and automations, and complete required trust/capability consent. Verify the new agent and report any remaining setup.
For a reviewed local package, use `openclaw templates inspect <path>`, then `openclaw templates add <path> --dry-run --json` to preview and `openclaw templates add <path>` to apply. The CLI accepts a local package directory or `CLAW.md` path, not ClawHub package coordinates. See [Template review and Add details](https://docs.openclaw.ai/cli/templates).
Manage installed skills
openclaw skills list
openclaw skills check
openclaw skills update my-skill
openclaw skills update --all
Use `--global` with `install` or `update` to manage skills shared by all local agents.
Remove an installed skill
Uninstall when the user asks. If the standalone ClawHub CLI is not installed, install it explicitly:
npm i -g clawhub
clawhub uninstall @owner/my-skill
The CLI asks for confirmation before removing the skill and its lockfile entry. Use the original agent workspace for agent-specific skills or the OpenClaw state directory for skills installed with `--global`:
clawhub --workdir /path/to/agent-workspace uninstall @owner/my-skill
clawhub --workdir ~/.openclaw uninstall @owner/my-skill
If `OPENCLAW_STATE_DIR` is set, use its value instead of `~/.openclaw`:
clawhub --workdir "$OPENCLAW_STATE_DIR" uninstall @owner/my-skill
The default skills watcher refreshes the available skills on the next agent turn. If watching is disabled, start a new session.
Publish skills
Install the standalone ClawHub CLI for publisher workflows:
npm i -g clawhub
clawhub login
clawhub whoami
Publish or sync skills:
clawhub skill publish ./my-skill
clawhub skill publish ./my-skill --version 1.2.3
clawhub sync --all
Notes
- Public registry: https://clawhub.ai
- `openclaw skills install` installs into the active workspace by default.
- Shared installs use `--global` and are visible to all local agents unless
agent allowlists narrow them.
Read more
name: clawhub description: "Search ClawHub for plugins by default, or skills and agent Templates when requested; add Templates; install, verify, update, uninstall, publish, or sync skills."
ClawHub
Prefer searching ClawHub for plugins unless the user asks for a skill or agent Template. Templates create new agents; skills extend the current agent. Search before claiming that a requested capability is unavailable.
Use `openclaw skills` for explicitly requested skill discovery and for managing skills for the current OpenClaw agent. Use the standalone `clawhub` CLI to uninstall installed ClawHub skills and for publishing, syncing, and publisher account workflows. Use the ClawHub registry for Template discovery and the Control UI for adding published Templates.
Discover plugins (default)
Use the `plugins` tool when available, with `action: "search"` and `query` set to the requested capability, to return native plugin search results. If the tool is unavailable, use the CLI:
openclaw plugins search "notion"
A discovery request does not authorize installation. Install only when the user asks.
Discover skills (explicit requests)
When the user explicitly asks for a skill, search skills instead of plugins:
openclaw skills search "postgres backups"
Install when the user asks. Verify the selected skill first and report the result.
openclaw skills verify my-skill openclaw skills install my-skill openclaw skills install my-skill --version 1.2.3
Discover and add Templates
Use **Pages → Templates** or fetch the public ClawHub registry:
GET https://clawhub.ai/api/v1/packages?family=template&limit=100 GET https://clawhub.ai/api/v1/packages/search?family=template&q=<URL-encoded-query>&limit=20
List responses have `items` and `nextCursor`; follow `cursor=<URL-encoded-cursor>` before claiming a complete inventory. Search responses have `results`. Use `category=<slug>` to filter. For broad availability questions, include current categories and representative entries with package names and short descriptions; distinguish category filters from categories with published entries. Discovery is read-only; the `plugins` tool searches plugins, not Templates.
When asked to install a Template, select its published release in **Pages → Templates → Add**. The page requires **Settings → Labs → Templates**; public registry reads do not. Explain that prerequisite if disabled. Review workspace files, skills/plugins, MCP servers, and automations, and complete required trust/capability consent. Verify the new agent and report any remaining setup.
For a reviewed local package, use `openclaw templates inspect <path>`, then `openclaw templates add <path> --dry-run --json` to preview and `openclaw templates add <path>` to apply. The CLI accepts a local package directory or `CLAW.md` path, not ClawHub package coordinates. See [Template review and Add details](https://docs.openclaw.ai/cli/templates).
Manage installed skills
openclaw skills list openclaw skills check openclaw skills update my-skill openclaw skills update --all
Use `--global` with `install` or `update` to manage skills shared by all local agents.
Remove an installed skill
Uninstall when the user asks. If the standalone ClawHub CLI is not installed, install it explicitly:
npm i -g clawhub clawhub uninstall @owner/my-skill
The CLI asks for confirmation before removing the skill and its lockfile entry. Use the original agent workspace for agent-specific skills or the OpenClaw state directory for skills installed with `--global`:
clawhub --workdir /path/to/agent-workspace uninstall @owner/my-skill clawhub --workdir ~/.openclaw uninstall @owner/my-skill
If `OPENCLAW_STATE_DIR` is set, use its value instead of `~/.openclaw`:
clawhub --workdir "$OPENCLAW_STATE_DIR" uninstall @owner/my-skill
The default skills watcher refreshes the available skills on the next agent turn. If watching is disabled, start a new session.
Publish skills
Install the standalone ClawHub CLI for publisher workflows:
npm i -g clawhub clawhub login clawhub whoami
Publish or sync skills:
clawhub skill publish ./my-skill clawhub skill publish ./my-skill --version 1.2.3 clawhub sync --all
Notes
- Public registry: https://clawhub.ai
- `openclaw skills install` installs into the active workspace by default.
- Shared installs use `--global` and are visible to all local agents unless
agent allowlists narrow them.
OpenClaw is an open-source AI assistant that runs on your own computer and meets you in the channels you already use: Discord, iMessage, Slack, Teams, Telegram, WhatsApp, and 20+ more, plus native apps for macOS, iOS, Android, Windows, and Linux.
Other skills on openclaw.
More skills from other plugins.
karpathy-guidelines
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
agent-builder
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…
Questions about clawhub.
- Which coding agents can use clawhub?
- clawhub installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

