openclaw skills
Inspect local skills, search ClawHub, install skills from ClawHub/Git/local
directories, verify ClawHub skills, and update ClawHub-tracked installs.
Related:
- Skills system: Skills
- Skill Workshop: Skill Workshop
- Skills config: Skills config
- ClawHub installs: ClawHub
Commands
search, update, and verify use ClawHub directly. install @owner/<slug>
installs a native ClawHub skill. install skills-sh:<owner>/<repo>/<slug> asks
ClawHub to resolve an external listing to its exact synchronized GitHub commit;
OpenClaw does not download from skills.sh. These entries are shown as
Not scanned by ClawHub, and that trust state is preserved through updates
and verification. Claimed or ClawHub-scanned skills use @owner/<slug>.
install git:owner/repo[@ref] clones an unmanaged Git skill, and install ./path copies a local skill directory. By default, install,
update, and verify 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.
Git and local directory installs expect SKILL.md at the source root. The
install slug comes from SKILL.md frontmatter name when it is valid, then
the source directory or repository name; use --as <slug> to override it.
--version is ClawHub-only. Skill installs do not support npm package specs
or zip/archive paths, and openclaw skills update updates ClawHub-tracked
installs only.
Gateway-backed skill dependency installs triggered from onboarding or Skills
settings use the separate skills.install request path instead.
Notes:
Community ClawHub skill installs and updates check trust before downloading.
Versioned community archive releases use exact-release trust metadata.
Resolver-backed GitHub skills rely on ClawHub’s install resolver to enforce
scan and force-install policy before it returns a pinned commit; use
--force-install to install a pending GitHub-backed skill before that scan
completes. Malicious or blocked community releases are refused. Risky
community releases require review and --acknowledge-clawhub-risk when a
non-interactive command should continue after that review. Official ClawHub
skill publishers and bundled OpenClaw skill sources bypass this release-trust
prompt.
Skill Workshop
openclaw skills workshop manages pending skill proposals in the selected
workspace. Proposals are not active skills until applied. For proposal
storage, support-file safeguards, Gateway methods, and approval policy, see
Skill Workshop.
propose-create, propose-update, and revise also accept --goal <text>
and --evidence <text> to record the proposal’s motivation and supporting
notes alongside the --proposal/--proposal-dir content.