ClawHub
ClawHub is the public registry where OpenClaw users can discover and publish skills and plugins. It gives self-hosting operators a catalog, version history, package files, source information, and security signals to review before adding a capability to their agent.
The registry is useful, but it is not a promise that every listing is official, compatible with every environment, or safe for every use. ClawHub is open to community publishing, so package inspection and permission controls remain part of installation.
Quick answer: Use the registry when you operate OpenClaw and want to add or update a specific community package. Use built-in or managed capabilities when you would rather start working without maintaining each local dependency yourself.
Who this is forNon-technical professionals, solopreneurs, and lean teams who want recurring browser, file, research, and monitoring workflows without self-hosting OpenClaw, configuring a server, or keeping a personal computer awake.
What Is ClawHub? The OpenClaw Skill & Plugin Registry
Official OpenClaw documentation defines ClawHub as its public registry for skills and plugins. It serves both users looking for capabilities and publishers releasing versioned packages.
| Package surface | What it contains | What the operator should review |
|---|---|---|
| Skill | A versioned text bundle centered on SKILL.md, with optional supporting files | Instructions, required tools, environment variables, scripts, and external services |
| Code plugin | Executable plugin code plus compatibility metadata | Source, publisher, permissions, dependencies, compatibility, and release history |
| Bundle plugin | A packaged collection of supported extension resources | Included components, provenance, configuration, and update behavior |
Public listings can show versions, tags, changelogs, files, source attribution, usage signals, and security scan summaries. Those details make packages easier to inspect; they do not replace source review.
The official explanation of how the registry works says publishing is open but subject to upload gates, automated checks, reports, and moderation. A listing should therefore be understood as discoverable community software unless its publisher and official status are clearly identified.
How to Install Skills From ClawHub
Use the current OpenClaw documentation rather than copying a command from an old tutorial. Package names, interfaces, compatibility requirements, and migration behavior can change.
A careful installation workflow has six stages:
- Search for the capability you need, not just the most popular title.
- Open the canonical listing and confirm the owner, source, published versions, files, and changelog.
- Read
SKILL.mdand inspect any scripts, packages, environment variables, credentials, or external services it requires. - Check compatibility and security signals, then decide whether the requested access matches the task.
- Use the current OpenClaw skills or plugins installation flow documented for that package type.
- Test the package in a restricted workspace before allowing it to reach important files, accounts, or browser sessions.
An installation can fail even when the package itself is valid. The host may be missing a binary, API key, browser capability, plugin interface, or permission that the package expects. Treat the listing's requirements as deployment inputs, not optional notes.
For current installation and update behavior, follow the official skills documentation and ClawHub guide.
Best OpenClaw Skills on ClawHub
There is no universal best package list. The catalog changes, and the right choice depends on the job, required access, maintenance quality, and fit with your environment.
Instead of ranking unfamiliar packages by downloads alone, shortlist them by outcome:
| Need | Useful skill category | Selection boundary |
|---|---|---|
| Repeatable research | Search, extraction, summarization, or source-management skills | Prefer clear source handling and bounded browser access |
| Document work | PDF, spreadsheet, writing, or transformation skills | Check file formats, temporary storage, and external upload behavior |
| Team operations | Messaging, ticketing, calendar, or reporting skills | Review account scopes and sender permissions |
| Developer workflows | Repository, testing, deployment, or diagnostics skills | Inspect every script and restrict command access |
| Media workflows | Image, audio, or video skills | Confirm provider accounts, output rights, and usage limits |
A stronger package usually has understandable instructions, visible source attribution, narrow requirements, a maintained release history, and permissions proportional to its purpose. Stars and downloads can help with discovery, but they do not prove security or suitability.
Use ClawHub-Compatible Skills (SKILL.md) Without Local Setup
MoClaw publicly describes its skill layer as OpenClaw-compatible and supports the SKILL.md pattern on a managed cloud computer. This lets users work with supported skill instructions without first operating an OpenClaw host, container stack, or local Gateway.
The practical distinction is who maintains the environment:
| Self-operated package workflow | Managed compatible-skill workflow |
|---|---|
| You install and update the runtime | The cloud environment is managed for you |
| You resolve system packages and scripts | Supported dependencies run in the managed workspace |
| You maintain uptime and recovery | The service handles the underlying environment |
| You configure every permission boundary | You still approve accounts, data, and task access |
Compatibility should not be read as a guarantee that every community package runs unchanged. A skill may assume a local path, operating-system feature, background service, unrestricted command, private binary, or credential flow that is unavailable in a managed environment.
Review custom skills before use and expect adjustments when their dependencies or system assumptions differ. MoClaw is a managed route for supported workflows, not a mirror of every package in the public registry.
50+ Built-In Skills vs Installing Each From ClawHub
MoClaw's public site advertises 50+ built-in skills alongside browser control, files, scheduled tasks, and its cloud computer. The purpose of that built-in layer is to cover common work before a user searches for another package.
| Decision point | 50+ built-in MoClaw skills | Individually installed registry packages |
|---|---|---|
| Starting effort | Available through the managed product | Requires discovery, review, installation, and configuration |
| Environment | Runs in MoClaw's managed cloud workspace | Runs in the operator's OpenClaw environment |
| Maintenance | Managed as part of the product | Package and runtime updates remain with the operator |
| Customization | Best for supported common workflows | Broader control over community and custom extensions |
| Compatibility work | Reduced for built-in capabilities | Depends on each package and host |
| Best fit | Users who want to assign work quickly | Technical operators who want package-level control |
Built-in does not mean unlimited or suitable for every task. Availability can depend on the account, connected services, model, permissions, and current product support. Check the MoClaw integrations page for the public capability list.
The two paths can complement each other: start with a supported capability, then add a reviewed compatible skill when a workflow needs specialized instructions.
Questions
Does Every ClawHub Skill Work With MoClaw?
No blanket compatibility claim is defensible. MoClaw supports OpenClaw-compatible skills, but an individual package may depend on scripts, binaries, paths, permissions, or services that require adaptation. Review the package requirements and test the workflow before relying on it.
Can a Skill Include Custom Scripts?
Yes. The official skill format allows supporting files, including scripts. That makes source inspection especially important because instructions may invoke executable code or external services. Use only the access needed for the task and avoid exposing unrelated credentials or files.
Does BYOK Change Which Skills I Can Use?
BYOK changes which supported model provider pays for and handles the model call. It does not automatically satisfy a skill's separate tool, service, package, or permission requirements. MoClaw publicly supports BYOK while keeping its supported skills, browser control, cloud computer, files, and schedules available. Check the current BYOK page for provider support.
Want common agent capabilities without maintaining each local package and dependency? Start with the managed skill layer, then add compatible custom workflows when the job requires them.
Want a claw without the setup?
MoClaw is a hosted cloud claw — OpenClaw-style automation, always on, with no Docker, VPS, or server to babysit. Bring your own key.