docs: rewrite community plugins page with Cards, Steps, and quality bar table

This commit is contained in:
Vincent Koc
2026-03-20 11:23:46 -07:00
parent fb293fa36f
commit e4d0fdcc15

View File

@@ -1,60 +1,95 @@
---
summary: "Community plugins: quality bar, hosting requirements, and PR submission path"
summary: "Community-maintained OpenClaw plugins: browse, install, and submit your own"
read_when:
- You want to publish a third-party OpenClaw plugin
- You want to propose a plugin for docs listing
title: "Community plugins"
- You want to find third-party OpenClaw plugins
- You want to publish or list your own plugin
title: "Community Plugins"
---
# Community plugins
# Community Plugins
This page tracks high-quality **community-maintained plugins** for OpenClaw.
Community plugins are third-party packages that extend OpenClaw with new
channels, tools, providers, or other capabilities. They are built and maintained
by the community, published on npm, and installable with a single command.
We accept PRs that add community plugins here when they meet the quality bar.
## Required for listing
- Plugin package is published on npmjs (installable via `openclaw plugins install <npm-spec>`).
- Source code is hosted on GitHub (public repository).
- Repository includes setup/use docs and an issue tracker.
- Plugin has a clear maintenance signal (active maintainer, recent updates, or responsive issue handling).
## How to submit
Open a PR that adds your plugin to this page with:
- Plugin name
- npm package name
- GitHub repository URL
- One-line description
- Install command
## Review bar
We prefer plugins that are useful, documented, and safe to operate.
Low-effort wrappers, unclear ownership, or unmaintained packages may be declined.
## Candidate format
Use this format when adding entries:
- **Plugin Name** — short description
npm: `@scope/package`
repo: `https://github.com/org/repo`
install: `openclaw plugins install @scope/package`
```bash
openclaw plugins install <npm-spec>
```
## Listed plugins
- **openclaw-dingtalk** — The OpenClaw DingTalk channel plugin enables the integration of enterprise robots using the Stream mode. It supports text, images and file messages via any DingTalk client.
npm: `@largezhou/ddingtalk`
repo: `https://github.com/largezhou/openclaw-dingtalk`
install: `openclaw plugins install @largezhou/ddingtalk`
- **QQbot** — Connect OpenClaw to QQ via the QQ Bot API. Supports private chats, group mentions, channel messages, and rich media including voice, images, videos, and files.
npm: `@sliverp/qqbot`
repo: `https://github.com/sliverp/qqbot`
install: `openclaw plugins install @sliverp/qqbot`
<CardGroup cols={1}>
<Card title="DingTalk" href="https://github.com/largezhou/openclaw-dingtalk">
Enterprise robot integration using Stream mode. Supports text, images, and
file messages via any DingTalk client.
- **WeChat** — Connect OpenClaw to WeChat personal accounts via WeChatPadPro (iPad protocol). Supports text, image, and file exchange with keyword-triggered conversations.
npm: `@icesword760/openclaw-wechat`
repo: `https://github.com/icesword0760/openclaw-wechat`
install: `openclaw plugins install @icesword760/openclaw-wechat`
```bash
openclaw plugins install @largezhou/ddingtalk
```
</Card>
<Card title="QQbot" href="https://github.com/sliverp/qqbot">
Connect to QQ via the QQ Bot API. Supports private chats, group mentions,
channel messages, and rich media including voice, images, videos, and files.
```bash
openclaw plugins install @sliverp/qqbot
```
</Card>
<Card title="WeChat" href="https://github.com/icesword0760/openclaw-wechat">
Connect to WeChat personal accounts via WeChatPadPro (iPad protocol).
Supports text, image, and file exchange with keyword-triggered conversations.
```bash
openclaw plugins install @icesword760/openclaw-wechat
```
</Card>
</CardGroup>
## Submit your plugin
We welcome community plugins that are useful, documented, and safe to operate.
<Steps>
<Step title="Publish to npm">
Your plugin must be installable via `openclaw plugins install \<npm-spec\>`.
See [Building Plugins](/plugins/building-plugins) for the full guide.
</Step>
<Step title="Host on GitHub">
Source code must be in a public repository with setup docs and an issue
tracker.
</Step>
<Step title="Open a PR">
Add your plugin to this page with:
- Plugin name
- npm package name
- GitHub repository URL
- One-line description
- Install command
</Step>
</Steps>
## Quality bar
| Requirement | Why |
| -------------------- | --------------------------------------------- |
| Published on npm | Users need `openclaw plugins install` 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 |
Low-effort wrappers, unclear ownership, or unmaintained packages may be declined.
## Related
- [Install and Configure Plugins](/tools/plugin) — how to install any plugin
- [Building Plugins](/plugins/building-plugins) — create your own
- [Plugin Manifest](/plugins/manifest) — manifest schema