Install an OpenClaw Skill

Inspect a third-party Skill before installing it. Registry metadata and scanners are useful signals, but the instructions and referenced files remain the real trust boundary.

Install from ClawHub

Use an owner-qualified reference to avoid publisher ambiguity:

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

By default, the Skill is installed into the active workspace. Add --global only when every local agent should be able to see the managed Skill.

Install from Git or a local folder

openclaw skills install git:owner/repo@ref
openclaw skills install ./path/to/skill --as my-skill

Git and local installs expect SKILL.md at the source root. Pin a reviewed Git reference instead of relying on a moving branch for a sensitive workflow.

Confirm eligibility

Check the Skill with OpenClaw, then start a new session. Skills may be filtered because a required binary, environment value, platform, or configuration flag is missing.

Expected result

The installed Skill appears under the intended name, verification does not report a failed trust state, and a matching task makes the Skill available to the agent.