@takibeiy/moltbot_cn 2026.1.28 → 2026.2.1-beta.1

package/skills/blucli/SKILL.md

@@ -2,7 +2,24 @@
 name: blucli
 description: BluOS CLI (blu) for discovery, playback, grouping, and volume.
 homepage: https://blucli.sh
-metadata: {"moltbot":{"emoji":"🫐","requires":{"bins":["blu"]},"install":[{"id":"go","kind":"go","module":"github.com/steipete/blucli/cmd/blu@latest","bins":["blu"],"label":"Install blucli (go)"}]}}
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "🫐",
+        "requires": { "bins": ["blu"] },
+        "install":
+          [
+            {
+              "id": "go",
+              "kind": "go",
+              "module": "github.com/steipete/blucli/cmd/blu@latest",
+              "bins": ["blu"],
+              "label": "Install blucli (go)",
+            },
+          ],
+      },
+  }
 ---
 
 # blucli (blu)
@@ -10,17 +27,20 @@ metadata: {"moltbot":{"emoji":"🫐","requires":{"bins":["blu"]},"install":[{"id
 Use `blu` to control Bluesound/NAD players.
 
 Quick start
+
 - `blu devices` (pick target)
 - `blu --device <id> status`
 - `blu play|pause|stop`
 - `blu volume set 15`
 
 Target selection (in priority order)
+
 - `--device <id|name|alias>`
 - `BLU_DEVICE`
 - config default (if set)
 
 Common tasks
+
 - Grouping: `blu group status|add|remove`
 - TuneIn search/play: `blu tunein search "query"`, `blu tunein play "query"`
 

package/skills/bluebubbles/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: bluebubbles
-description: Build or update the BlueBubbles external channel plugin for Moltbot (extension package, REST send/probe, webhook inbound).
+description: Build or update the BlueBubbles external channel plugin for OpenClaw (extension package, REST send/probe, webhook inbound).
 ---
 
 # BlueBubbles plugin
@@ -8,6 +8,7 @@ description: Build or update the BlueBubbles external channel plugin for Moltbot
 Use this skill when working on the BlueBubbles channel plugin.
 
 ## Layout
+
 - Extension package: `extensions/bluebubbles/` (entry: `index.ts`).
 - Channel implementation: `extensions/bluebubbles/src/channel.ts`.
 - Webhook handling: `extensions/bluebubbles/src/monitor.ts` (register via `api.registerHttpHandler`).
@@ -16,6 +17,7 @@ Use this skill when working on the BlueBubbles channel plugin.
 - Catalog entry for onboarding: `src/channels/plugins/catalog.ts`.
 
 ## Internal helpers (use these, not raw API calls)
+
 - `probeBlueBubbles` in `extensions/bluebubbles/src/probe.ts` for health checks.
 - `sendMessageBlueBubbles` in `extensions/bluebubbles/src/send.ts` for text delivery.
 - `resolveChatGuidForTarget` in `extensions/bluebubbles/src/send.ts` for chat lookup.
@@ -25,15 +27,18 @@ Use this skill when working on the BlueBubbles channel plugin.
 - `buildBlueBubblesApiUrl` + `blueBubblesFetchWithTimeout` in `extensions/bluebubbles/src/types.ts` for shared REST plumbing.
 
 ## Webhooks
+
 - BlueBubbles posts JSON to the gateway HTTP server.
 - Normalize sender/chat IDs defensively (payloads vary by version).
 - Skip messages marked as from self.
-- Route into core reply pipeline via the plugin runtime (`api.runtime`) and `clawdbot/plugin-sdk` helpers.
+- Route into core reply pipeline via the plugin runtime (`api.runtime`) and `openclaw/plugin-sdk` helpers.
 - For attachments/stickers, use `<media:...>` placeholders when text is empty and attach media paths via `MediaUrl(s)` in the inbound context.
 
 ## Config (core)
+
 - `channels.bluebubbles.serverUrl` (base URL), `channels.bluebubbles.password`, `channels.bluebubbles.webhookPath`.
 - Action gating: `channels.bluebubbles.actions.reactions` (default true).
 
 ## Message tool notes
+
 - **Reactions:** The `react` action requires a `target` (phone number or chat identifier) in addition to `messageId`. Example: `action=react target=+15551234567 messageId=ABC123 emoji=❤️`

package/skills/camsnap/SKILL.md

@@ -2,7 +2,24 @@
 name: camsnap
 description: Capture frames or clips from RTSP/ONVIF cameras.
 homepage: https://camsnap.ai
-metadata: {"moltbot":{"emoji":"📸","requires":{"bins":["camsnap"]},"install":[{"id":"brew","kind":"brew","formula":"steipete/tap/camsnap","bins":["camsnap"],"label":"Install camsnap (brew)"}]}}
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "📸",
+        "requires": { "bins": ["camsnap"] },
+        "install":
+          [
+            {
+              "id": "brew",
+              "kind": "brew",
+              "formula": "steipete/tap/camsnap",
+              "bins": ["camsnap"],
+              "label": "Install camsnap (brew)",
+            },
+          ],
+      },
+  }
 ---
 
 # camsnap
@@ -10,10 +27,12 @@ metadata: {"moltbot":{"emoji":"📸","requires":{"bins":["camsnap"]},"install":[
 Use `camsnap` to grab snapshots, clips, or motion events from configured cameras.
 
 Setup
+
 - Config file: `~/.config/camsnap/config.yaml`
 - Add camera: `camsnap add --name kitchen --host 192.168.0.10 --user user --pass pass`
 
 Common commands
+
 - Discover: `camsnap discover --info`
 - Snapshot: `camsnap snap kitchen --out shot.jpg`
 - Clip: `camsnap clip kitchen --dur 5s --out clip.mp4`
@@ -21,5 +40,6 @@ Common commands
 - Doctor: `camsnap doctor --probe`
 
 Notes
+
 - Requires `ffmpeg` on PATH.
 - Prefer a short test capture before longer clips.

package/skills/canvas/SKILL.md

@@ -1,10 +1,11 @@
 # Canvas Skill
 
-Display HTML content on connected Moltbot nodes (Mac app, iOS, Android).
+Display HTML content on connected OpenClaw nodes (Mac app, iOS, Android).
 
 ## Overview
 
 The canvas tool lets you present web content on any connected node's canvas view. Great for:
+
 - Displaying games, visualizations, dashboards
 - Showing generated HTML content
 - Interactive demos
@@ -29,14 +30,15 @@ The canvas tool lets you present web content on any connected node's canvas view
 
 The canvas host server binds based on `gateway.bind` setting:
 
-| Bind Mode | Server Binds To | Canvas URL Uses |
-|-----------|-----------------|-----------------|
-| `loopback` | 127.0.0.1 | localhost (local only) |
-| `lan` | LAN interface | LAN IP address |
-| `tailnet` | Tailscale interface | Tailscale hostname |
-| `auto` | Best available | Tailscale > LAN > loopback |
+| Bind Mode  | Server Binds To     | Canvas URL Uses            |
+| ---------- | ------------------- | -------------------------- |
+| `loopback` | 127.0.0.1           | localhost (local only)     |
+| `lan`      | LAN interface       | LAN IP address             |
+| `tailnet`  | Tailscale interface | Tailscale hostname         |
+| `auto`     | Best available      | Tailscale > LAN > loopback |
 
 **Key insight:** The `canvasHostHostForBridge` is derived from `bridgeHost`. When bound to Tailscale, nodes receive URLs like:
+
 ```
 http://<tailscale-hostname>:18793/__moltbot__/canvas/<file>.html
 ```
@@ -45,17 +47,17 @@ This is why localhost URLs don't work - the node receives the Tailscale hostname
 
 ## Actions
 
-| Action | Description |
-|--------|-------------|
-| `present` | Show canvas with optional target URL |
-| `hide` | Hide the canvas |
-| `navigate` | Navigate to a new URL |
-| `eval` | Execute JavaScript in the canvas |
-| `snapshot` | Capture screenshot of canvas |
+| Action     | Description                          |
+| ---------- | ------------------------------------ |
+| `present`  | Show canvas with optional target URL |
+| `hide`     | Hide the canvas                      |
+| `navigate` | Navigate to a new URL                |
+| `eval`     | Execute JavaScript in the canvas     |
+| `snapshot` | Capture screenshot of canvas         |
 
 ## Configuration
 
-In `~/.clawdbot/moltbot.json`:
+In `~/.openclaw/openclaw.json`:
 
 ```json
 {
@@ -74,6 +76,7 @@ In `~/.clawdbot/moltbot.json`:
 ### Live Reload
 
 When `liveReload: true` (default), the canvas host:
+
 - Watches the root directory for changes (via chokidar)
 - Injects a WebSocket client into HTML files
 - Automatically reloads connected canvases when files change
@@ -101,15 +104,18 @@ HTML
 ### 2. Find your canvas host URL
 
 Check how your gateway is bound:
+
 ```bash
-cat ~/.clawdbot/moltbot.json | jq '.gateway.bind'
+cat ~/.openclaw/openclaw.json | jq '.gateway.bind'
 ```
 
 Then construct the URL:
+
 - **loopback**: `http://127.0.0.1:18793/__moltbot__/canvas/<file>.html`
 - **lan/tailnet/auto**: `http://<hostname>:18793/__moltbot__/canvas/<file>.html`
 
 Find your Tailscale hostname:
+
 ```bash
 tailscale status --json | jq -r '.Self.DNSName' | sed 's/\.$//'
 ```
@@ -117,7 +123,7 @@ tailscale status --json | jq -r '.Self.DNSName' | sed 's/\.$//'
 ### 3. Find connected nodes
 
 ```bash
-moltbot nodes list
+openclaw nodes list
 ```
 
 Look for Mac/iOS/Android nodes with canvas capability.
@@ -129,6 +135,7 @@ canvas action:present node:<node-id> target:<full-url>
 ```
 
 **Example:**
+
 ```
 canvas action:present node:mac-63599bc4-b54d-4392-9048-b97abd58343a target:http://peters-mac-studio-1.sheep-coho.ts.net:18793/__moltbot__/canvas/snake.html
 ```
@@ -148,7 +155,8 @@ canvas action:hide node:<node-id>
 **Cause:** URL mismatch between server bind and node expectation.
 
 **Debug steps:**
-1. Check server bind: `cat ~/.clawdbot/moltbot.json | jq '.gateway.bind'`
+
+1. Check server bind: `cat ~/.openclaw/openclaw.json | jq '.gateway.bind'`
 2. Check what port canvas is on: `lsof -i :18793`
 3. Test URL directly: `curl http://<hostname>:18793/__moltbot__/canvas/<file>.html`
 
@@ -160,11 +168,12 @@ Always specify `node:<node-id>` parameter.
 
 ### "node not connected" error
 
-Node is offline. Use `moltbot nodes list` to find online nodes.
+Node is offline. Use `openclaw nodes list` to find online nodes.
 
 ### Content not updating
 
 If live reload isn't working:
+
 1. Check `liveReload: true` in config
 2. Ensure file is in the canvas root directory
 3. Check for watcher errors in logs

package/skills/clawhub/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: clawhub
+description: Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.
+metadata:
+  {
+    "openclaw":
+      {
+        "requires": { "bins": ["clawhub"] },
+        "install":
+          [
+            {
+              "id": "node",
+              "kind": "node",
+              "package": "clawhub",
+              "bins": ["clawhub"],
+              "label": "Install ClawHub CLI (npm)",
+            },
+          ],
+      },
+  }
+---
+
+# ClawHub CLI
+
+Install
+
+```bash
+npm i -g clawhub
+```
+
+Auth (publish)
+
+```bash
+clawhub login
+clawhub whoami
+```
+
+Search
+
+```bash
+clawhub search "postgres backups"
+```
+
+Install
+
+```bash
+clawhub install my-skill
+clawhub install my-skill --version 1.2.3
+```
+
+Update (hash-based match + upgrade)
+
+```bash
+clawhub update my-skill
+clawhub update my-skill --version 1.2.3
+clawhub update --all
+clawhub update my-skill --force
+clawhub update --all --no-input --force
+```
+
+List
+
+```bash
+clawhub list
+```
+
+Publish
+
+```bash
+clawhub publish ./my-skill --slug my-skill --name "My Skill" --version 1.2.0 --changelog "Fixes + docs"
+```
+
+Notes
+
+- Default registry: https://clawhub.com (override with CLAWHUB_REGISTRY or --registry)
+- Default workdir: cwd (falls back to OpenClaw workspace); install dir: ./skills (override with --workdir / --dir / CLAWHUB_WORKDIR)
+- Update command hashes local files, resolves matching version, and upgrades to latest unless --version is set

package/skills/coding-agent/SKILL.md

@@ -1,7 +1,10 @@
 ---
 name: coding-agent
 description: Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
-metadata: {"moltbot":{"emoji":"🧩","requires":{"anyBins":["claude","codex","opencode","pi"]}}}
+metadata:
+  {
+    "openclaw": { "emoji": "🧩", "requires": { "anyBins": ["claude", "codex", "opencode", "pi"] } },
+  }
 ---
 
 # Coding Agent (bash-first)
@@ -24,27 +27,27 @@ bash command:"codex exec 'Your prompt'"
 
 ### Bash Tool Parameters
 
-| Parameter | Type | Description |
-|-----------|------|-------------|
-| `command` | string | The shell command to run |
-| `pty` | boolean | **Use for coding agents!** Allocates a pseudo-terminal for interactive CLIs |
-| `workdir` | string | Working directory (agent sees only this folder's context) |
-| `background` | boolean | Run in background, returns sessionId for monitoring |
-| `timeout` | number | Timeout in seconds (kills process on expiry) |
-| `elevated` | boolean | Run on host instead of sandbox (if allowed) |
+| Parameter    | Type    | Description                                                                 |
+| ------------ | ------- | --------------------------------------------------------------------------- |
+| `command`    | string  | The shell command to run                                                    |
+| `pty`        | boolean | **Use for coding agents!** Allocates a pseudo-terminal for interactive CLIs |
+| `workdir`    | string  | Working directory (agent sees only this folder's context)                   |
+| `background` | boolean | Run in background, returns sessionId for monitoring                         |
+| `timeout`    | number  | Timeout in seconds (kills process on expiry)                                |
+| `elevated`   | boolean | Run on host instead of sandbox (if allowed)                                 |
 
 ### Process Tool Actions (for background sessions)
 
-| Action | Description |
-|--------|-------------|
-| `list` | List all running/recent sessions |
-| `poll` | Check if session is still running |
-| `log` | Get session output (with optional offset/limit) |
-| `write` | Send raw data to stdin |
-| `submit` | Send data + newline (like typing and pressing Enter) |
-| `send-keys` | Send key tokens or hex bytes |
-| `paste` | Paste text (with optional bracketed mode) |
-| `kill` | Terminate the session |
+| Action      | Description                                          |
+| ----------- | ---------------------------------------------------- |
+| `list`      | List all running/recent sessions                     |
+| `poll`      | Check if session is still running                    |
+| `log`       | Get session output (with optional offset/limit)      |
+| `write`     | Send raw data to stdin                               |
+| `submit`    | Send data + newline (like typing and pressing Enter) |
+| `send-keys` | Send key tokens or hex bytes                         |
+| `paste`     | Paste text (with optional bracketed mode)            |
+| `kill`      | Terminate the session                                |
 
 ---
 
@@ -99,13 +102,14 @@ process action:kill sessionId:XXX
 
 ### Flags
 
-| Flag | Effect |
-|------|--------|
-| `exec "prompt"` | One-shot execution, exits when done |
-| `--full-auto` | Sandboxed but auto-approves in workspace |
-| `--yolo` | NO sandbox, NO approvals (fastest, most dangerous) |
+| Flag            | Effect                                             |
+| --------------- | -------------------------------------------------- |
+| `exec "prompt"` | One-shot execution, exits when done                |
+| `--full-auto`   | Sandboxed but auto-approves in workspace           |
+| `--yolo`        | NO sandbox, NO approvals (fastest, most dangerous) |
 
 ### Building/Creating
+
 ```bash
 # Quick one-shot (auto-approves) - remember PTY!
 bash pty:true workdir:~/project command:"codex exec --full-auto 'Build a dark mode toggle'"
@@ -116,7 +120,7 @@ bash pty:true workdir:~/project background:true command:"codex --yolo 'Refactor
 
 ### Reviewing PRs
 
-**⚠️ CRITICAL: Never review PRs in Moltbot's own project folder!**
+**⚠️ CRITICAL: Never review PRs in OpenClaw's own project folder!**
 Clone to temp folder or use git worktree.
 
 ```bash
@@ -133,6 +137,7 @@ bash pty:true workdir:/tmp/pr-130-review command:"codex review --base main"
 ```
 
 ### Batch PR Reviews (parallel army!)
+
 ```bash
 # Fetch all PR refs first
 git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'
@@ -227,7 +232,7 @@ git worktree remove /tmp/issue-99
 6. **vanilla for reviewing** - no special flags needed
 7. **Parallel is OK** - run many Codex processes at once for batch work
 8. **NEVER start Codex in ~/clawd/** - it'll read your soul docs and get weird ideas about the org chart!
-9. **NEVER checkout branches in ~/Projects/moltbot/** - that's the LIVE Moltbot instance!
+9. **NEVER checkout branches in ~/Projects/openclaw/** - that's the LIVE OpenClaw instance!
 
 ---
 
@@ -249,20 +254,21 @@ This prevents the user from seeing only "Agent failed before reply" and having n
 
 ## Auto-Notify on Completion
 
-For long-running background tasks, append a wake trigger to your prompt so Moltbot gets notified immediately when the agent finishes (instead of waiting for the next heartbeat):
+For long-running background tasks, append a wake trigger to your prompt so OpenClaw gets notified immediately when the agent finishes (instead of waiting for the next heartbeat):
 
 ```
 ... your task here.
 
 When completely finished, run this command to notify me:
-moltbot gateway wake --text "Done: [brief summary of what was built]" --mode now
+openclaw gateway wake --text "Done: [brief summary of what was built]" --mode now
 ```
 
 **Example:**
+
 ```bash
 bash pty:true workdir:~/project background:true command:"codex --yolo exec 'Build a REST API for todos.
 
-When completely finished, run: moltbot gateway wake --text \"Done: Built todos REST API with CRUD endpoints\" --mode now'"
+When completely finished, run: openclaw gateway wake --text \"Done: Built todos REST API with CRUD endpoints\" --mode now'"
 ```
 
 This triggers an immediate wake event — Skippy gets pinged in seconds, not 10 minutes.
@@ -275,4 +281,4 @@ This triggers an immediate wake event — Skippy gets pinged in seconds, not 10
 - **Git repo required:** Codex won't run outside a git directory. Use `mktemp -d && git init` for scratch work.
 - **exec is your friend:** `codex exec "prompt"` runs and exits cleanly - perfect for one-shots.
 - **submit vs write:** Use `submit` to send input + Enter, `write` for raw data without newline.
-- **Sass works:** Codex responds well to playful prompts. Asked it to write a haiku about being second fiddle to a space lobster, got: *"Second chair, I code / Space lobster sets the tempo / Keys glow, I follow"* 🦞
+- **Sass works:** Codex responds well to playful prompts. Asked it to write a haiku about being second fiddle to a space lobster, got: _"Second chair, I code / Space lobster sets the tempo / Keys glow, I follow"_ 🦞

package/skills/discord/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: discord
-description: Use when you need to control Discord from Moltbot via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
-metadata: {"moltbot":{"emoji":"🎮","requires":{"config":["channels.discord"]}}}
+description: Use when you need to control Discord from OpenClaw via the discord tool: send messages, react, post or upload stickers, upload emojis, run polls, manage threads/pins/search, create/edit/delete channels and categories, fetch permissions or member/role/channel info, or handle moderation actions in Discord DMs or channels.
+metadata: {"openclaw":{"emoji":"🎮","requires":{"config":["channels.discord"]}}}
 ---
 
 # Discord Actions
 
 ## Overview
 
-Use `discord` to manage messages, reactions, threads, polls, and moderation. You can disable groups via `discord.actions.*` (defaults to enabled, except roles/moderation). The tool uses the bot token configured for Moltbot.
+Use `discord` to manage messages, reactions, threads, polls, and moderation. You can disable groups via `discord.actions.*` (defaults to enabled, except roles/moderation). The tool uses the bot token configured for OpenClaw.
 
 ## Inputs to collect
 
@@ -84,8 +84,8 @@ Message context lines include `discord message id` and `channel` fields you can
 {
   "action": "stickerUpload",
   "guildId": "999",
-  "name": "moltbot_wave",
-  "description": "Moltbot waving hello",
+  "name": "openclaw_wave",
+  "description": "OpenClaw waving hello",
   "tags": "👋",
   "mediaUrl": "file:///tmp/wave.png"
 }
@@ -131,6 +131,7 @@ Message context lines include `discord message id` and `channel` fields you can
 ## Action gating
 
 Use `discord.actions.*` to disable action groups:
+
 - `reactions` (react + reactions list + emojiList)
 - `stickers`, `polls`, `permissions`, `messages`, `threads`, `pins`, `search`
 - `emojiUploads`, `stickerUploads`
@@ -138,6 +139,7 @@ Use `discord.actions.*` to disable action groups:
 - `roles` (role add/remove, default `false`)
 - `channels` (channel/category create/edit/delete/move, default `false`)
 - `moderation` (timeout/kick/ban, default `false`)
+
 ### Read recent messages
 
 ```json
@@ -172,7 +174,7 @@ Use `discord.actions.*` to disable action groups:
 {
   "action": "sendMessage",
   "to": "channel:123",
-  "content": "Hello from Moltbot"
+  "content": "Hello from OpenClaw"
 }
 ```
 
@@ -435,6 +437,7 @@ Create, edit, delete, and move channels and categories. Enable via `discord.acti
 **Keep it conversational!** Discord is a chat platform, not documentation.
 
 ### Do
+
 - Short, punchy messages (1-3 sentences ideal)
 - Multiple quick replies > one wall of text
 - Use emoji for tone/emphasis 🦞
@@ -443,6 +446,7 @@ Create, edit, delete, and move channels and categories. Enable via `discord.acti
 - Match the energy of the conversation
 
 ### Don't
+
 - No markdown tables (Discord renders them as ugly raw `| text |`)
 - No `## Headers` for casual chat (use **bold** or CAPS for emphasis)
 - Avoid multi-paragraph essays
@@ -450,6 +454,7 @@ Create, edit, delete, and move channels and categories. Enable via `discord.acti
 - Skip the "I'd be happy to help!" fluff
 
 ### Formatting that works
+
 - **bold** for emphasis
 - `code` for technical terms
 - Lists for multiple items
@@ -459,6 +464,7 @@ Create, edit, delete, and move channels and categories. Enable via `discord.acti
 ### Example transformations
 
 ❌ Bad:
+
 ```
 I'd be happy to help with that! Here's a comprehensive overview of the versioning strategies available:
 
@@ -470,6 +476,7 @@ CalVer uses date-based versions like...
 ```
 
 ✅ Good:
+
 ```
 versioning options: semver (1.2.3), calver (2026.01.04), or yolo (`latest` forever). what fits your release cadence?
 ```

package/skills/eightctl/SKILL.md

@@ -2,7 +2,24 @@
 name: eightctl
 description: Control Eight Sleep pods (status, temperature, alarms, schedules).
 homepage: https://eightctl.sh
-metadata: {"moltbot":{"emoji":"🎛️","requires":{"bins":["eightctl"]},"install":[{"id":"go","kind":"go","module":"github.com/steipete/eightctl/cmd/eightctl@latest","bins":["eightctl"],"label":"Install eightctl (go)"}]}}
+metadata:
+  {
+    "openclaw":
+      {
+        "emoji": "🎛️",
+        "requires": { "bins": ["eightctl"] },
+        "install":
+          [
+            {
+              "id": "go",
+              "kind": "go",
+              "module": "github.com/steipete/eightctl/cmd/eightctl@latest",
+              "bins": ["eightctl"],
+              "label": "Install eightctl (go)",
+            },
+          ],
+      },
+  }
 ---
 
 # eightctl
@@ -10,20 +27,24 @@ metadata: {"moltbot":{"emoji":"🎛️","requires":{"bins":["eightctl"]},"instal
 Use `eightctl` for Eight Sleep pod control. Requires auth.
 
 Auth
+
 - Config: `~/.config/eightctl/config.yaml`
 - Env: `EIGHTCTL_EMAIL`, `EIGHTCTL_PASSWORD`
 
 Quick start
+
 - `eightctl status`
 - `eightctl on|off`
 - `eightctl temp 20`
 
 Common tasks
+
 - Alarms: `eightctl alarm list|create|dismiss`
 - Schedules: `eightctl schedule list|create|update`
 - Audio: `eightctl audio state|play|pause`
 - Base: `eightctl base info|angle`
 
 Notes
+
 - API is unofficial and rate-limited; avoid repeated logins.
 - Confirm before changing temperature or alarms.

package/skills/food-order/SKILL.md

@@ -2,7 +2,7 @@
 name: food-order
 description: Reorder Foodora orders + track ETA/status with ordercli. Never confirm without explicit user approval. Triggers: order food, reorder, track ETA.
 homepage: https://ordercli.sh
-metadata: {"moltbot":{"emoji":"🥡","requires":{"bins":["ordercli"]},"install":[{"id":"go","kind":"go","module":"github.com/steipete/ordercli/cmd/ordercli@latest","bins":["ordercli"],"label":"Install ordercli (go)"}]}}
+metadata: {"openclaw":{"emoji":"🥡","requires":{"bins":["ordercli"]},"install":[{"id":"go","kind":"go","module":"github.com/steipete/ordercli/cmd/ordercli@latest","bins":["ordercli"],"label":"Install ordercli (go)"}]}}
 ---
 
 # Food order (Foodora via ordercli)
@@ -10,32 +10,39 @@ metadata: {"moltbot":{"emoji":"🥡","requires":{"bins":["ordercli"]},"install":
 Goal: reorder a previous Foodora order safely (preview first; confirm only on explicit user “yes/confirm/place the order”).
 
 Hard safety rules
+
 - Never run `ordercli foodora reorder ... --confirm` unless user explicitly confirms placing the order.
 - Prefer preview-only steps first; show what will happen; ask for confirmation.
 - If user is unsure: stop at preview and ask questions.
 
 Setup (once)
+
 - Country: `ordercli foodora countries` → `ordercli foodora config set --country AT`
 - Login (password): `ordercli foodora login --email you@example.com --password-stdin`
 - Login (no password, preferred): `ordercli foodora session chrome --url https://www.foodora.at/ --profile "Default"`
 
 Find what to reorder
+
 - Recent list: `ordercli foodora history --limit 10`
 - Details: `ordercli foodora history show <orderCode>`
 - If needed (machine-readable): `ordercli foodora history show <orderCode> --json`
 
 Preview reorder (no cart changes)
+
 - `ordercli foodora reorder <orderCode>`
 
 Place reorder (cart change; explicit confirmation required)
+
 - Confirm first, then run: `ordercli foodora reorder <orderCode> --confirm`
 - Multiple addresses? Ask user for the right `--address-id` (take from their Foodora account / prior order data) and run:
   - `ordercli foodora reorder <orderCode> --confirm --address-id <id>`
 
 Track the order
+
 - ETA/status (active list): `ordercli foodora orders`
 - Live updates: `ordercli foodora orders --watch`
 - Single order detail: `ordercli foodora order <orderCode>`
 
 Debug / safe testing
+
 - Use a throwaway config: `ordercli --config /tmp/ordercli.json ...`