Install, update, and verify OpenClaw skills

Operational sequence

1. 1

   Search

   Use an intent query and inspect owners before choosing a slug.

   openclaw skills search "calendar" --json

   Copy
2. 2

   Verify

   Review registry decision, version selector, scan state, and pinned source when returned.

   openclaw skills verify @owner/skill --json

   Copy
3. 3

   Install a reviewed version

   Warnings require explicit review; blocks cannot be overridden by force.

   openclaw skills install @owner/skill --version <version>

   Copy
4. 4

   Check readiness

   Confirm required binaries, env, config, and actual agent visibility.

   openclaw skills check --json
   openclaw skills info <name> --json

   Copy
5. 5

   Update deliberately

   Local edits are preserved unless a force update is explicitly chosen.

   openclaw skills update @owner/skill

   Copy

Trust and removal boundaries

• A pending or unscanned release is not equivalent to a verified official package.
• An acknowledgement flag records acceptance of a warning; it does not turn the skill into trusted code.
• Review commands, services, credentials, external writes, and broad triggers again after every update.
• Use the documented ClawHub uninstall flow with the same workspace/global root where the skill was installed.