feat: add native clawhub install flows

docs/cli/index.md

@@ -485,6 +485,9 @@ List and inspect available skills plus readiness info.
 
 Subcommands:
 
+- `skills search [query...]`: search ClawHub skills.
+- `skills install <slug>`: install a skill from ClawHub into the active workspace.
+- `skills update <slug|--all>`: update tracked ClawHub skills.
 - `skills list`: list skills (default when no subcommand).
 - `skills info <name>`: show details for one skill.
 - `skills check`: summary of ready vs missing requirements.
@@ -495,7 +498,7 @@ Options:
 - `--json`: output JSON (no styling).
 - `-v`, `--verbose`: include missing requirements detail.
 
-Tip: use `npx clawhub` to search, install, and sync skills.
+Tip: use `openclaw skills search`, `openclaw skills install`, and `openclaw skills update` for ClawHub-backed skills.
 
 ### `pairing`
 

docs/cli/plugins.md

@@ -48,6 +48,7 @@ capabilities.
 ```bash
 openclaw plugins install <path-or-spec>
 openclaw plugins install <npm-spec> --pin
+openclaw plugins install clawhub:<package>
 openclaw plugins install <plugin>@<marketplace>
 openclaw plugins install <plugin> --marketplace <marketplace>
 ```
@@ -71,6 +72,18 @@ Supported archives: `.zip`, `.tgz`, `.tar.gz`, `.tar`.
 
 Claude marketplace installs are also supported.
 
+ClawHub installs use an explicit `clawhub:<package>` locator:
+
+```bash
+openclaw plugins install clawhub:openclaw-codex-app-server
+openclaw plugins install clawhub:openclaw-codex-app-server@1.2.3
+```
+
+OpenClaw downloads the package archive from ClawHub, checks the advertised
+plugin API / minimum gateway compatibility, then installs it through the normal
+archive path. Recorded installs keep their ClawHub source metadata for later
+updates.
+
 Use `plugin@marketplace` shorthand when the marketplace name exists in Claude's
 local registry cache at `~/.claude/plugins/known_marketplaces.json`:
 
@@ -144,8 +157,8 @@ openclaw plugins update <id-or-npm-spec> --dry-run
 openclaw plugins update @openclaw/voice-call@beta
 ```
 
-Updates apply to tracked installs in `plugins.installs`, currently npm and
-marketplace installs.
+Updates apply to tracked installs in `plugins.installs`, including npm,
+ClawHub, and marketplace installs.
 
 When you pass a plugin id, OpenClaw reuses the recorded install spec for that
 plugin. That means previously stored dist-tags such as `@beta` and exact pinned

docs/cli/skills.md

@@ -1,14 +1,15 @@
 ---
-summary: "CLI reference for `openclaw skills` (list/info/check) and skill eligibility"
+summary: "CLI reference for `openclaw skills` (search/install/update/list/info/check)"
 read_when:
   - 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
 title: "skills"
 ---
 
 # `openclaw skills`
 
-Inspect skills (bundled + workspace + managed overrides) and see what’s eligible vs missing requirements.
+Inspect local skills and install/update skills from ClawHub.
 
 Related:
 
@@ -19,8 +20,17 @@ Related:
 ## Commands
 
 ```bash
+openclaw skills search "calendar"
+openclaw skills install <slug>
+openclaw skills install <slug> --version <version>
+openclaw skills update <slug>
+openclaw skills update --all
 openclaw skills list
 openclaw skills list --eligible
 openclaw skills info <name>
 openclaw skills check
 ```
+
+`search`/`install`/`update` use ClawHub directly and install into the active
+workspace `skills/` directory. `list`/`info`/`check` still inspect the local
+skills visible to the current workspace and config.