How to Install OpenClaw Skills: ClawHub, Git, Local & Global

To install an OpenClaw skill, first choose the source: ClawHub, Git, or a local directory. Then decide whether the skill belongs only to the active workspace or should be shared globally across local agents.

The fastest current path for a ClawHub skill is:

openclaw skills install @owner/<slug>

This guide covers the current install commands, where skills land, how to verify them, and how to separate install failures from trigger, dependency, and permission problems.

TL;DR

The commands above follow the current OpenClaw Skills documentation and CLI reference.

1. Choose the right install source

Use the source that matches what you actually have:

If you are still looking for a skill rather than installing one, browse the OpenClaw skills directory. Do not turn an install problem into a discovery problem.

2. Install from ClawHub

For a ClawHub skill:

openclaw skills install @owner/<slug>

Replace @owner/<slug> with the owner-qualified skill reference from the listing.

By default, the current OpenClaw docs say openclaw skills install installs into the active workspace skills/ directory. This is the right default when the skill belongs to one workspace or agent workflow.

Install globally

To share the managed skill across local agents:

openclaw skills install @owner/<slug> --global

Global managed skills live under:

~/.openclaw/skills

Agent allowlists can still narrow which agents see them.

3. Install from a Git repository

Use the native Git source form:

openclaw skills install git:owner/repo@ref

This is clearer than manually cloning a repository into an arbitrary skill folder because OpenClaw handles the install source directly.

Current OpenClaw documentation notes that Git installs expect SKILL.md at the source root. Before installing, inspect the repository and confirm the skill layout matches that expectation.

For a third-party repository, review at least:

• SKILL.md
• scripts and executable files
• requested binaries and environment variables
• network or shell behavior
• repository ownership and maintenance history

For a deeper review path, use the OpenClaw Skill Security Checklist.

4. Install from a local skill directory

For a directory already on your machine:

openclaw skills install ./path/to/skill --as my-tool

The --as value gives the installed skill an explicit slug when you need to override the inferred name.

A minimal local skill needs a SKILL.md file. If you are building your own, follow How to Create a Custom OpenClaw Skill with SKILL.md.

5. Understand where OpenClaw loads skills from

The current OpenClaw Skills docs describe multiple sources with precedence. Higher-priority locations can override the same-named skill from lower-priority locations.

This matters when a skill appears installed but behaves differently than expected: another skill with the same name may have higher precedence.

6. Verify the installation before testing behavior

First confirm OpenClaw can see the installed skill.

openclaw skills list

Then check current skill state:

openclaw skills check

When you need details for one skill:

openclaw skills info <skill-name>

For ClawHub skills, verify the published trust envelope:

openclaw skills verify @owner/<slug>

A skill being present in a list is not the same as the skill successfully completing your task. Verify discovery first, then test behavior separately.

7. Run one low-risk behavior test

Use a request that clearly matches the skill's purpose and does not expose sensitive data or broad permissions.

A useful sequence is:

1. Confirm the skill is listed.
2. Confirm required binaries and configuration are available.
3. Start a fresh test context when needed.
4. Send one narrow request that matches the skill description.
5. Compare the actual result with the skill's documented behavior.

If the skill is installed but never selected, use the Skill Installed but Not Triggered Fix Checklist.

8. Update installed skills

For workspace ClawHub installs:

openclaw skills update --all

For shared managed skills:

openclaw skills update --all --global

The current official docs distinguish tracked ClawHub updates from Git or local sources; Git and local sources should be reinstalled when you need to refresh them.

9. Fix common installation failures

Skill does not appear in the list

Check in this order:

1. Did the install command finish successfully?
2. Are you looking at the intended workspace?
3. Did you install with --global when you meant workspace scope, or the reverse?
4. Does the source contain a valid SKILL.md?
5. Is another same-named skill taking precedence?

Do not start by rewriting the skill description if OpenClaw cannot discover the skill at all.

Skill appears but is not used

That is usually a routing or eligibility problem, not an installation problem.

Check:

• whether the request clearly matches the skill description
• whether the skill is visible to the active agent
• whether required binaries, environment values, or config gates are satisfied
• whether another skill overlaps the same task

Use the dedicated not-triggered checklist for this branch.

Skill starts but fails with a dependency error

Separate the dependency layer from installation.

Use How to Fix a Missing Dependency in OpenClaw Skills when a required CLI, binary, package, or runtime is absent.

Skill fails with permission denied

There are two different intents on this site:

• filesystem/install errors such as EACCES or EPERM: OpenClaw Skill Permission Denied Guide
• a narrow missing scope: operator.read failure: How to Fix missing scope: operator.read

Choose the guide that matches the actual error instead of applying a generic permissions fix.

10. Use a real verification worksheet

Do not copy an example matrix that pretends an environment passed. Record what you actually ran.

Mark a row as passed only after the real install and behavior test succeed in that environment.

11. Safer third-party installation checklist

Before enabling a third-party skill:

• confirm the publisher and exact source
• read SKILL.md
• inspect scripts and executable paths
• identify required binaries, secrets, and network access
• use the narrowest practical permissions
• test with low-risk inputs first
• document the source and installed scope

OpenClaw's current official Skills docs explicitly warn that third-party skills should be treated as untrusted code. A successful install does not prove a skill is safe.

FAQ

What is the current command to install an OpenClaw skill?

For a ClawHub skill, use:

openclaw skills install @owner/<slug>

How do I install an OpenClaw skill from GitHub?

Use the documented Git source form:

openclaw skills install git:owner/repo@ref

Review the repository first and confirm SKILL.md is at the expected source root.

Should I install a skill globally?

Use --global when the skill should be managed under ~/.openclaw/skills and shared across local agents. Use workspace scope when the skill belongs to one workspace or workflow.

Do I always need to restart after installing a skill?

Do not assume a universal restart rule. Current OpenClaw documentation describes session snapshots and refresh behavior; first verify the skill with openclaw skills list and openclaw skills check, then start a fresh test context when your current session still reflects older state.

Why is the skill installed but not working?

First identify the failing layer: discovery, routing, dependency, permission, credentials, or runtime behavior. The OpenClaw Skill Troubleshooting Guide helps separate those branches.

Next step

After installation:

• Create a custom OpenClaw skill
• Review a skill before installing it
• Troubleshoot common skill errors
• Browse OpenClaw skills