f7d7148cf0
Source-grounded rewrite of 529 published docs pages with per-unit information-loss verification: 1,713 factual corrections cited to src/**, generated surfaces regenerated, frontmatter titles preserved for i18n, release notes pages untouched. All docs gates green. Closes #100141
2.7 KiB
summary, read_when, title, doc-schema-version
| summary | read_when | title | doc-schema-version | ||
|---|---|---|---|---|---|
| Find and publish community-maintained OpenClaw plugins |
|
Community plugins | 1 |
Community plugins are third-party packages that extend OpenClaw with channels, tools, providers, hooks, or other capabilities. Use ClawHub as the primary discovery surface for public community plugins.
Find plugins
Search ClawHub from the CLI:
openclaw plugins search "calendar"
Install a ClawHub plugin with an explicit source prefix:
openclaw plugins install clawhub:<package-name>
npm remains a supported direct-install path during the launch cutover:
openclaw plugins install npm:<package-name>
Use Manage plugins for common install, update,
inspect, and uninstall examples. Use openclaw plugins for
the full command reference and source-selection rules.
Publish plugins
Publish public community plugins on ClawHub so OpenClaw users can discover and install them. ClawHub owns the live package listing, release history, scan status, and install hints; the docs do not maintain a static third-party plugin catalog.
clawhub package publish your-org/your-plugin --dry-run
clawhub package publish your-org/your-plugin
Before publishing, make sure the plugin has package metadata, a plugin manifest, setup docs, and a clear maintenance owner. ClawHub validates owner scope, package name, version, file limits, and source metadata before creating a release, then keeps new releases hidden from normal install and download surfaces until review and verification finish.
Checklist before you publish:
| Requirement | Why |
|---|---|
| Published on ClawHub | Users need openclaw plugins install hints to work |
| Public GitHub repo | Source review, issue tracking, transparency |
| Setup and usage docs | Users need to know how to configure it |
| Active maintenance | Recent updates or responsive issue handling |
Full publishing contract:
- ClawHub publishing - owners, scopes, releases, review, package validation, and package transfer
- Building plugins - the plugin package shape and first publish workflow
- Plugin manifest - native plugin manifest fields
Related
- Plugins - install, configure, restart, and troubleshoot
- Manage plugins - command examples
- ClawHub publishing - publish and release rules