10 · Skills and plugins

A skill supplies task instructions and may include scripts or resources. A plugin adds runtime capabilities or integrations. Installing either can change what code runs or which data becomes accessible.

Inspect before adding

openclaw skills list
openclaw skills check
openclaw plugins list

Read the source, prerequisites, maintainer history, and requested access. Missing dependencies can make an installed skill unusable; installation alone is not a successful workflow test.

Current skill syntax

In the reviewed release, replace @owner/skill-name with an exact ClawHub identifier. The placeholder is not an actual recommendation. Do not include square brackets around it:

openclaw skills install @owner/skill-name
openclaw skills verify @owner/skill-name
openclaw skills update @owner/skill-name

These are separate operations: install after review, verify the installed entry, and update only when intended. Updates here apply to ClawHub-tracked installs; local and Git sources have different lifecycle rules. Older versions may differ—check openclaw skills --help.

Keep the set small

Add one useful extension, run a low-risk task, and retain it only if it works. A scanner or marketplace badge is supporting evidence, not a guarantee of safety. Use the plugins reference for plugin packages; they are not interchangeable with skill folders.