Clawhub
Search ClawHub for plugins by default, or skills when explicitly requested; install, verify, update, uninstall, publish, or sync skills.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Clawhub when an AI agent needs a reusable SKILL.md workflow for this job: Search ClawHub for plugins by default, or skills when explicitly requested; install, verify, update, uninstall, publish, or sync skills.
When not to use it
Skip Clawhub when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/clawhub # Save SKILL.md to ~/.claude/skills/clawhub/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/clawhub/SKILL.md. For a shared project, commit the folder at .claude/skills/clawhub/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Clawhub skill for this task: Use Clawhub when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 74/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# ClawHub
Prefer searching ClawHub for plugins unless the user explicitly asks for a skill. 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.
## 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:
```bash 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:
```bash openclaw skills search "postgres backups" ```
Install when the user asks. Verify the selected skill first and report the result.
```bash openclaw skills verify my-skill openclaw skills install my-skill openclaw skills install my-skill --version 1.2.3 ```
## Manage installed skills
```bash 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:
```bash 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`:
```bash 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`:
```bash 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:
```bash npm i -g clawhub clawhub login clawhub whoami ```
Publish or sync skills:
```bash 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.
Intended uses
- Use Clawhub when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.