OpenClaw Plugins Guide

A Skill provides instructions in SKILL.md. A plugin adds runtime code and can register tools, channels, model providers, hooks, services, or packaged Skills. That larger capability also creates a larger trust boundary.

Inspect the inventory

openclaw plugins list
openclaw plugins --help

Use the Installed view in Control UI or the CLI inventory to confirm the plugin origin, installed version, enabled state, and capabilities. Do not install a similarly named package simply because a config migration suggests a missing integration; confirm the official package identifier first.

Install deliberately

Plugins may come from the official catalog, ClawHub, npm, git, a local directory, or an archive. Before installation, review:

• Publisher and repository
• Package manifest and install scripts
• Requested tools, secrets, network access, and hooks
• Version pin or update behavior
• Whether the same task can be solved by a narrower Skill

After installation, restart or reload only when the plugin documentation requires it, then run:

openclaw doctor
openclaw status --all
openclaw plugins list

Disable before removal

If a plugin behaves unexpectedly, disable it first and verify that the Gateway becomes healthy. Remove its configuration and secrets only after you know which data belongs to the plugin. Keep a record of the previous version when an update causes a regression.

Expected result

• The plugin appears once in the inventory.
• Its origin and enabled state are clear.
• Doctor reports no missing dependency or manifest problem.
• Only the intended tools, channel, or provider becomes available.

Use Plugin not loading when the inventory and effective capabilities disagree.