chore: update openclaw naming
This commit is contained in:
@@ -956,7 +956,7 @@ Use managed overrides instead of editing the repo copy. Put your changes in `~/.
|
||||
|
||||
### Can I load skills from a custom folder
|
||||
|
||||
Yes. Add extra directories via `skills.load.extraDirs` in `~/.openclaw/openclaw.json` (lowest precedence). Default precedence remains: `<workspace>/skills` → `~/.openclaw/skills` → bundled → `skills.load.extraDirs`. `clawdhub` installs into `./skills` by default, which OpenClaw treats as `<workspace>/skills`.
|
||||
Yes. Add extra directories via `skills.load.extraDirs` in `~/.openclaw/openclaw.json` (lowest precedence). Default precedence remains: `<workspace>/skills` → `~/.openclaw/skills` → bundled → `skills.load.extraDirs`. `clawhub` installs into `./skills` by default, which OpenClaw treats as `<workspace>/skills`.
|
||||
|
||||
### How can I use different models for different tasks
|
||||
|
||||
@@ -1000,17 +1000,17 @@ Docs: [Cron jobs](/automation/cron-jobs), [Cron vs Heartbeat](/automation/cron-v
|
||||
|
||||
### How do I install skills on Linux
|
||||
|
||||
Use **ClawdHub** (CLI) or drop skills into your workspace. The macOS Skills UI isn’t available on Linux.
|
||||
Browse skills at https://clawdhub.com.
|
||||
Use **ClawHub** (CLI) or drop skills into your workspace. The macOS Skills UI isn’t available on Linux.
|
||||
Browse skills at https://clawhub.com.
|
||||
|
||||
Install the ClawdHub CLI (pick one package manager):
|
||||
Install the ClawHub CLI (pick one package manager):
|
||||
|
||||
```bash
|
||||
npm i -g clawdhub
|
||||
npm i -g clawhub
|
||||
```
|
||||
|
||||
```bash
|
||||
pnpm add -g clawdhub
|
||||
pnpm add -g clawhub
|
||||
```
|
||||
|
||||
### Can OpenClaw run tasks on a schedule or continuously in the background
|
||||
@@ -1076,11 +1076,11 @@ targeting those APIs.
|
||||
Install skills:
|
||||
|
||||
```bash
|
||||
clawdhub install <skill-slug>
|
||||
clawdhub update --all
|
||||
clawhub install <skill-slug>
|
||||
clawhub update --all
|
||||
```
|
||||
|
||||
ClawdHub installs into `./skills` under your current directory (or falls back to your configured OpenClaw workspace); OpenClaw treats that as `<workspace>/skills` on the next session. For shared skills across agents, place them in `~/.openclaw/skills/<name>/SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [ClawdHub](/tools/clawdhub).
|
||||
ClawHub installs into `./skills` under your current directory (or falls back to your configured OpenClaw workspace); OpenClaw treats that as `<workspace>/skills` on the next session. For shared skills across agents, place them in `~/.openclaw/skills/<name>/SKILL.md`. Some skills expect binaries installed via Homebrew; on Linux that means Linuxbrew (see the Homebrew Linux FAQ entry above). See [Skills](/tools/skills) and [ClawHub](/tools/clawhub).
|
||||
|
||||
### How do I install the Chrome extension for browser takeover
|
||||
|
||||
|
||||
Reference in New Issue
Block a user