Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.openclaw.ai/llms.txt

Use this file to discover all available pages before exploring further.

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 when you want OpenClaw users to 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 it creates a release, then keeps new releases hidden from normal install and download surfaces until review and verification finish. Use this checklist before you publish:
RequirementWhy
Published on ClawHubUsers need openclaw plugins install hints to work
Public GitHub repoSource review, issue tracking, transparency
Setup and usage docsUsers need to know how to configure it
Active maintenanceRecent updates or responsive issue handling
Use these pages for the full publishing contract: