Files
openclaw/docs/cli/skills.md
clawsweeper[bot] 5702858553 feat(cli): support installing skills to shared global directory via --global (#83705)
Summary:
- Adds `--global` to `openclaw skills install` and `openclaw skills update`, routing ClawHub installs and updates to the shared managed skills root with docs, changelog, and CLI command tests.
- Reproducibility: not applicable. as a bug reproduction; this is a new CLI feature request. Source inspection confirms current `main` lacks `--global`, and the source PR includes after-fix terminal proof for the new path.

Automerge notes:
- PR branch already contained follow-up commit before automerge: fix(cli): address skills global review
- PR branch already contained follow-up commit before automerge: feat(cli): support installing skills to shared global directory via -…

Validation:
- ClawSweeper review passed for head 6eb7187fc1.
- Required merge gates passed before the squash merge.

Prepared head SHA: 6eb7187fc1
Review: https://github.com/openclaw/openclaw/pull/83705#issuecomment-4480023577

Co-authored-by: Hongwei Ma <marvae24@gmail.com>
Co-authored-by: clawsweeper <274271284+clawsweeper[bot]@users.noreply.github.com>
Co-authored-by: clawsweeper[bot] <274271284+clawsweeper[bot]@users.noreply.github.com>
Approved-by: takhoffman
Co-authored-by: takhoffman <781889+takhoffman@users.noreply.github.com>
2026-05-18 17:22:00 +00:00

3.2 KiB

summary, read_when, title
summary read_when title
CLI reference for `openclaw skills` (search/install/update/list/info/check)
You want to see which skills are available and ready to run
You want to search, install, or update skills from ClawHub
You want to debug missing binaries/env/config for skills
Skills

openclaw skills

Inspect local skills and install/update skills from ClawHub.

Related:

Commands

openclaw skills search "calendar"
openclaw skills search --limit 20 --json
openclaw skills install <slug>
openclaw skills install <slug> --version <version>
openclaw skills install <slug> --force
openclaw skills install <slug> --agent <id>
openclaw skills install <slug> --global
openclaw skills update <slug>
openclaw skills update <slug> --global
openclaw skills update --all
openclaw skills update --all --agent <id>
openclaw skills update --all --global
openclaw skills list
openclaw skills list --eligible
openclaw skills list --json
openclaw skills list --verbose
openclaw skills list --agent <id>
openclaw skills info <name>
openclaw skills info <name> --json
openclaw skills info <name> --agent <id>
openclaw skills check
openclaw skills check --agent <id>
openclaw skills check --json

search/install/update use ClawHub directly. By default, install and update target the active workspace skills/ directory; with --global, they target the shared managed skills directory. list/info/check still inspect the local skills visible to the current workspace and config. Workspace-backed commands resolve the target workspace from --agent <id>, then the current working directory when it is inside a configured agent workspace, then the default agent.

This CLI install command downloads skill folders from ClawHub. Gateway-backed skill dependency installs triggered from onboarding or Skills settings use the separate skills.install request path instead.

Notes:

  • search [query...] accepts an optional query; omit it to browse the default ClawHub search feed.
  • search --limit <n> caps returned results.
  • install --force overwrites an existing workspace skill folder for the same slug.
  • --global targets the shared managed skills directory and cannot be combined with --agent <id>.
  • --agent <id> targets one configured agent workspace and overrides current working directory inference.
  • update <slug> updates a single tracked skill. Add --global to target the shared managed skills directory instead of the workspace.
  • update --all updates tracked ClawHub installs in the selected workspace, or in the shared managed skills directory when combined with --global.
  • check --agent <id> checks the selected agent's workspace and reports which ready skills are actually visible to that agent's prompt or command surface.
  • list is the default action when no subcommand is provided.
  • list, info, and check write their rendered output to stdout. With --json, that means the machine-readable payload stays on stdout for pipes and scripts.