Install Guide

Follow these steps to install OpenClaw and manage openclaw skills safely.

Step 1 - Install the runtime

OpenClaw provides official installer scripts for macOS, Linux, and Windows.

$ curl -fsSL https://openclaw.bot/install.sh | bash

Non-root friendly CLI installer:

$ curl -fsSL https://openclaw.bot/install-cli.sh | bash

Windows (PowerShell):

iwr -useb https://openclaw.ai/install.ps1 | iex

Installer help:

curl -fsSL https://openclaw.bot/install.sh | bash -s -- --help

& ([scriptblock]::Create((iwr -useb https://openclaw.ai/install.ps1))) -?

Step 2 - Install the ClawHub CLI

The ClawHub CLI lets you search, install, and manage openclaw skills.

npm i -g clawhub

pnpm add -g clawhub

Step 3 - Search and install skills

Use search to find a skill, then install it into your workspace.

clawhub search "calendar"

clawhub install <skill-slug>

clawhub list

Start a new OpenClaw session so the newly installed skill is loaded.

Step 4 - Update and sync (optional)

Keep your openclaw skills current and share usage data when desired.

clawhub update --all

clawhub sync --all

Step 5 - Where skills are stored

By default, ClawHub installs skills into ./skills under the current working directory. If an OpenClaw workspace is configured, it falls back to that workspace unless you override --workdir or CLAWHUB_WORKDIR.

OpenClaw loads workspace skills from <workspace>/skills, and those skills take precedence over bundled or managed skills.

Step 6 - Lockfile and telemetry

Installed skills are recorded in .clawhub/lock.json inside your workdir. When you run clawhub sync while logged in, a minimal telemetry snapshot is sent to compute install counts. You can disable it:

export CLAWHUB_DISABLE_TELEMETRY=1

Optional - Onboard the workspace

The OpenClaw onboarding flow can install the daemon and walk you through setup.

openclaw onboard --install-daemon

Troubleshooting

If the installer completes but the openclaw command is missing, open a new terminal or fix your Node/npm PATH. Re-running the installer help command can confirm the flags available for your environment.

Review permissions and dependencies before installing skills. High-risk skills should be tested in a sandbox.