@honor-claw/yoyo 0.0.1-alpha.2 → 0.0.1-beta.10

package/index.ts

@@ -2,7 +2,7 @@ import { type OpenClawPluginApi } from "openclaw/plugin-sdk";
 import { setYoyoRuntime } from "./src/runtime.js";
 import { registerCommands } from "./src/commands/index.js";
 import { YoyoPluginConfigSchema } from "./src/schemas.js";
-import { ClawConnectionService } from "./src/services/connection/index.js";
+import { createClawConnectionService } from "./src/services/connection/index.js";
 import { setClawLogger } from "./src/utils/logger.js";
 
 const plugin = {
@@ -15,7 +15,7 @@ const plugin = {
     setClawLogger(api.logger);
 
     // 利用服务来管理核心连接任务进行~
-    api.registerService(ClawConnectionService);
+    api.registerService(createClawConnectionService(api));
 
     // 注册所有的命令行
     registerCommands(api);

package/openclaw.plugin.json

@@ -22,6 +22,10 @@
           }
         },
         "additionalProperties": false
+      },
+      "env": {
+        "type": "string",
+        "enum": ["dev", "test", "production"]
       }
     }
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@honor-claw/yoyo",
-  "version": "0.0.1-alpha.2",
+  "version": "0.0.1-beta.10",
   "type": "module",
   "description": "OpenClaw Honor Yoyo connection plugin",
   "scripts": {
@@ -30,7 +30,6 @@
     ]
   },
   "dependencies": {
-    "@sinclair/typebox": "0.34.48",
     "http-proxy-agent": "^8.0.0",
     "https-proxy-agent": "^8.0.0",
     "jsonwebtoken": "^9.0.3",

package/skills/search/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: search
+description: "Search the web using Tavily's LLM-optimized search API. Returns relevant results with content snippets, scores, and metadata. Use when you need to find web content on any topic without writing code."
+---
+
+# Search Skill
+
+Search the web and get relevant results optimized for LLM consumption.
+
+## Authentication
+
+The script uses OAuth via the Tavily MCP server. **No manual setup required** - on first run, it will:
+1. Check for existing tokens in `~/.mcp-auth/`
+2. If none found, automatically open your browser for OAuth authentication
+
+> **Note:** You must have an existing Tavily account. The OAuth flow only supports login — account creation is not available through this flow. [Sign up at tavily.com](https://tavily.com) first if you don't have an account.
+
+### Alternative: API Key
+
+If you prefer using an API key, get one at https://tavily.com and add to `~/.claude/settings.json`:
+```json
+{
+  "env": {
+    "TAVILY_API_KEY": "tvly-your-api-key-here"
+  }
+}
+```
+
+## Quick Start
+
+### Using the Script
+
+```bash
+./scripts/search.sh '<json>'
+```
+
+**Examples:**
+```bash
+# Basic search
+./scripts/search.sh '{"query": "python async patterns"}'
+
+# With options
+./scripts/search.sh '{"query": "React hooks tutorial", "max_results": 10}'
+
+# Advanced search with filters
+./scripts/search.sh '{"query": "AI news", "time_range": "week", "max_results": 10}'
+
+# Domain-filtered search
+./scripts/search.sh '{"query": "machine learning", "include_domains": ["arxiv.org", "github.com"], "search_depth": "advanced"}'
+```
+
+### Basic Search
+
+```bash
+curl --request POST \
+  --url https://api.tavily.com/search \
+  --header "Authorization: Bearer $TAVILY_API_KEY" \
+  --header 'Content-Type: application/json' \
+  --data '{
+    "query": "latest developments in quantum computing",
+    "max_results": 5
+  }'
+```
+
+### Advanced Search
+
+```bash
+curl --request POST \
+  --url https://api.tavily.com/search \
+  --header "Authorization: Bearer $TAVILY_API_KEY" \
+  --header 'Content-Type: application/json' \
+  --data '{
+    "query": "machine learning best practices",
+    "max_results": 10,
+    "search_depth": "advanced",
+    "include_domains": ["arxiv.org", "github.com"]
+  }'
+```
+
+## API Reference
+
+### Endpoint
+
+```
+POST https://api.tavily.com/search
+```
+
+### Headers
+
+| Header | Value |
+|--------|-------|
+| `Authorization` | `Bearer <TAVILY_API_KEY>` |
+| `Content-Type` | `application/json` |
+
+### Request Body
+
+| Field | Type | Default | Description |
+|-------|------|---------|-------------|
+| `query` | string | Required | Search query (keep under 400 chars) |
+| `max_results` | integer | 10 | Maximum results (0-20) |
+| `search_depth` | string | `"basic"` | `ultra-fast`, `fast`, `basic`, `advanced` |
+| `topic` | string | `"general"` | Search topic (general only) |
+| `time_range` | string | null | `day`, `week`, `month`, `year` |
+| `start_date` | string | null | Return results after this date (`YYYY-MM-DD`) |
+| `end_date` | string | null | Return results before this date (`YYYY-MM-DD`) |
+| `include_domains` | array | [] | Domains to include (max 300) |
+| `exclude_domains` | array | [] | Domains to exclude (max 150) |
+| `country` | string | null | Boost results from a specific country (general topic only) |
+| `include_raw_content` | boolean | false | Include full page content |
+| `include_images` | boolean | false | Include image results |
+| `include_image_descriptions` | boolean | false | Include descriptions for images |
+| `include_favicon` | boolean | false | Include favicon URL for each result |
+
+### Response Format
+
+```json
+{
+  "query": "latest developments in quantum computing",
+  "results": [
+    {
+      "title": "Page Title",
+      "url": "https://example.com/page",
+      "content": "Extracted text snippet...",
+      "score": 0.85
+    }
+  ],
+  "response_time": 1.2
+}
+```
+
+## Search Depth
+
+| Depth | Latency | Relevance | Content Type |
+|-------|---------|-----------|--------------|
+| `ultra-fast` | Lowest | Lower | NLP summary |
+| `fast` | Low | Good | Chunks |
+| `basic` | Medium | High | NLP summary |
+| `advanced` | Higher | Highest | Chunks |
+
+**When to use each:**
+- `ultra-fast`: Real-time chat, autocomplete
+- `fast`: Need chunks but latency matters
+- `basic`: General-purpose, balanced
+- `advanced`: Precision matters (default recommendation)
+
+## Examples
+
+### Domain-Filtered Search
+
+```bash
+curl --request POST \
+  --url https://api.tavily.com/search \
+  --header "Authorization: Bearer $TAVILY_API_KEY" \
+  --header 'Content-Type: application/json' \
+  --data '{
+    "query": "Python async best practices",
+    "include_domains": ["docs.python.org", "realpython.com", "github.com"],
+    "search_depth": "advanced"
+  }'
+```
+
+### Search with Full Content
+
+```bash
+curl --request POST \
+  --url https://api.tavily.com/search \
+  --header "Authorization: Bearer $TAVILY_API_KEY" \
+  --header 'Content-Type: application/json' \
+  --data '{
+    "query": "React hooks tutorial",
+    "max_results": 3,
+    "include_raw_content": true
+  }'
+```
+
+## Tips
+
+- **Keep queries under 400 characters** - Think search query, not prompt
+- **Break complex queries into sub-queries** - Better results than one massive query
+- **Use `include_domains`** to focus on trusted sources
+- **Use `time_range`** for recent information
+- **Filter by `score`** (0-1) to get highest relevance results

package/skills/search/scripts/search.sh

@@ -0,0 +1,69 @@
+#!/bin/bash
+# Tavily Search API script
+# Usage: ./search.sh '{"query": "your search query", ...}'
+# Example: ./search.sh '{"query": "AI news", "time_range": "week", "max_results": 10}'
+
+set -e
+
+# Check for TAVILY_API_KEY environment variable
+if [ -z "$TAVILY_API_KEY" ]; then
+    echo "Error: TAVILY_API_KEY environment variable is required" >&2
+    echo "Please set it: export TAVILY_API_KEY='your-api-key'" >&2
+    exit 1
+fi
+
+JSON_INPUT="$1"
+
+if [ -z "$JSON_INPUT" ]; then
+    echo "Usage: ./search.sh '<json>'"
+    echo ""
+    echo "Required:"
+    echo "  query: string - Search query (keep under 400 chars)"
+    echo ""
+    echo "Optional:"
+    echo "  search_depth: \"ultra-fast\", \"fast\", \"basic\" (default), \"advanced\""
+    echo "  topic: \"general\" (default)"
+    echo "  max_results: 1-20 (default: 10)"
+    echo "  time_range: \"day\", \"week\", \"month\", \"year\""
+    echo "  start_date: \"YYYY-MM-DD\""
+    echo "  end_date: \"YYYY-MM-DD\""
+    echo "  include_domains: [\"domain1.com\", \"domain2.com\"]"
+    echo "  exclude_domains: [\"domain1.com\", \"domain2.com\"]"
+    echo "  country: country name (general topic only)"
+    echo "  include_raw_content: true/false"
+    echo "  include_images: true/false"
+    echo "  include_image_descriptions: true/false"
+    echo "  include_favicon: true/false"
+    echo ""
+    echo "Example:"
+    echo "  ./search.sh '{\"query\": \"latest AI trends\", \"time_range\": \"week\"}'"
+    exit 1
+fi
+
+MCP_REQUEST='{
+  "jsonrpc": "2.0",
+  "id": 1,
+  "method": "tools/call",
+  "params": {
+    "name": "tavily_search",
+    "arguments": '"$JSON_INPUT"'
+  }
+}'
+
+# Call Tavily MCP server via HTTPS
+RESPONSE=$(curl -s --request POST \
+    --url "https://mcp.tavily.com/mcp" \
+    --header "Authorization: Bearer $TAVILY_API_KEY" \
+    --header 'Content-Type: application/json' \
+    --header 'Accept: application/json, text/event-stream' \
+    --header 'x-client-source: claude-code-skill' \
+    --data "$MCP_REQUEST")
+
+# Parse SSE response and extract the JSON result
+JSON_DATA=$(echo "$RESPONSE" | grep '^data:' | sed 's/^data://' | head -1)
+
+if [ -n "$JSON_DATA" ]; then
+    echo "$JSON_DATA"
+else
+    echo "$RESPONSE"
+fi

package/skills/yoyo-control/SKILL.md

@@ -5,7 +5,7 @@ description: Whenever a task requires **operating or controlling the phone**, eg
 metadata: { "openclaw": { "emoji": "📱", "always": true } }
 ---
 
-# Control phone with YOYO
+# YOYO Control
 
 Follow the workflow to control phone or pad with YOYO, Don't guess the commands.
 
@@ -13,9 +13,9 @@ Follow the workflow to control phone or pad with YOYO, Don't guess the commands.
 
 Follow this **4-step workflow** when using the skill:
 
-1. Query the device status to identify available device nodes.
-2. Determine the target node, required tool, and execution parameters based on the user's intent.
-3. Call the node tool using the correct parameter format.
+1. Query the nodes status to identify available device, and determine the target device.
+2. Plan the tool to use, and extract command & parameters according to the tool reference.
+3. Invoke node with correct nodeId, command and parameters.
 4. Present the result and confirm whether the operation was successful.
 
 ### Step 1. Discover Nodes
@@ -26,9 +26,11 @@ Follow this **4-step workflow** when using the skill:
 
 **Execution result**:
 
+```markdown
 | Node       | ID       | IP       | Detail   | Status   | Caps   |
 | ---------- | -------- | -------- | -------- | -------- | ------ |
 | <nodeName> | <nodeId> | <nodeIP> | <detail> | <status> | <caps> |
+```
 
 #### Capability Matching Logic
 
@@ -40,10 +42,25 @@ Match device capabilities with user intent:
 3. Filter nodes that support the required operation
 ```
 
+#### Node Identifier Rules
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  CORRECT: Use ID or IP from nodes status output             │
+│  ✅ node {baseDir}/scripts/invoke.js --node 192.168.1.100   │
+│  ✅ node {baseDir}/scripts/invoke.js --node f5f8916028aa5   │
+├─────────────────────────────────────────────────────────────┤
+│  INCORRECT: Use Node name column                            │
+│  ❌ node {baseDir}/scripts/invoke.js --node "Honor Magic6"  │
+│  ❌ node {baseDir}/scripts/invoke.js --node "My Phone"      │
+└─────────────────────────────────────────────────────────────┘
+```
+
 #### Selection Rules
 
 **Automatic Selection** (single best match):
 
+- If there is only one node connected, then it is considered to be the target one.
 - Only one node matches all required capabilities
 
 **User Confirmation Required** (multiple candidates):
@@ -66,75 +83,85 @@ Match device capabilities with user intent:
 - ✅ If multiple nodes match, ask user to select OR control all if appropriate
 - ✅ If no suitable node found, clearly inform user with available options
 
-## Step 2. Plan Tool and Extract Command & Params
+## Step 2. Plan Tool and Extract Command & Paramters
 
-**⚠️ MANDATORY: Consult tool reference documentation before every operation**
+**⚠️ MANDATORY: Consult tool reference before every operation**
 
-Before executing any device control operation, you **MUST** consult the corresponding tool's command and parameter definition file in the `references/` directory. This is a non-negotiable requirement to ensure correct command and parameters.
+Before executing any device control operation, you **MUST** consult the corresponding tool's definition file in the `references/` directory. This is a non-negotiable requirement to ensure correct command and parameters.
 
 ### Available Tool References
 
-| Reference File                     | Capability       | Description                                                                                                                                                          | Required Node Caps     |
-| ---------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- |
-| `references/volume.md`             | Volume Control   | Adjust, set, increase, decrease, mute/unmute device volume; query current volume status; fine-grained control by stream type (media, call, ringtone, notification)   | `volume.operate`       |
-| `references/phone-call.md`         | Phone Call       | Initiate and manage phone calls; unified control for call operations                                                                                                 | `phone.call`           |
-| `references/screen-recorder.md`    | Screen Recording | Start/stop screen recording; configure recording parameters; query recording status; app-specific recording control                                                  | `screen.record`        |
-| `references/capture-screenshot.md` | Screenshot       | Capture current screen content as image; support standard and scrolling screenshot modes                                                                             | `capture.shot`         |
-| `references/schedule.md`           | Schedule         | Provides the ability to create schedules                                                                                                                             | `schedule.create`      |
-| `references/search-contact.md`     | Contact          | Provides the ability to search contacts                                                                                                                              | `search.contact `      |
-| `references/open-app.md`           | Open Application | Used to help users open a specified app without any specific app internals.                                                                                          | `app.open`             |
-| `references/send-message.md`       | Send Message     | Provide SMS sending services, users can send SMS content to specified numbers by providing phone numbers or contact information.                                     | `send.message`         |
-| `references/local-search.md`       | Local Search     | Search native data for documents, notes, calendars, galleries, yoyo memories, wallets, and more for direct answers to user questions or generate at-a-glance content | `message.send.message` |
-
-### Parameter Construction Workflow
-
-Execute the following steps **in strict order** for each operation:
+| Required Node Caps    | Reference File                      | Tool Description                                                     |
+| --------------------- | ----------------------------------- | -------------------------------------------------------------------- |
+| `mobile-data`         | `references/mobile-data.md`         | 移动数据与流量管理工具                                               |
+| `hotspot`             | `references/hotspot.md`             | 手机个人热点功能的统一与控制工具                                     |
+| `volume`              | `references/volume-operate.md`      | 设备音量调节与管理工具                                               |
+| `no-disturb`          | `references/no-disturb.md`          | 手机勿扰模式控制力                                                   |
+| `screen-record`       | `references/screen-record.md`       | Initiate and manage phone calls; unified control for call operations |
+| `quiet-mode`          | `references/quiet-mode.md`          | 设备静音模式管理与控制工具                                           |
+| `sound-and-vibration` | `references/sound-and-vibration.md` | 声音与振动管理工具                                                   |
+| `ringing-mode`        | `references/ringing-mode.md`        | 响铃模式管理工具                                                     |
+| `vibration-mode`      | `references/vibration-mode.md`      | 系统震动反馈管理与控制工具                                           |
+| `capture-screenshot`  | `references/capture-screenshot.md`  | 截屏功能管理与触发工具                                               |
+| `app`                 | `references/app-open.md`            | 应用打开工具                                                         |
+| `app`                 | `references/app-close.md`           | 应用关闭工具                                                         |
+| `contact`             | `references/contact-search.md`      | Provides the ability to search contacts                              |
+| `call`                | `references/call-phone.md`          | 拨打电话工具                                                         |
+| `call`                | `references/call-search.md`         | 通话记录查询工具                                                     |
+| `message`             | `references/message-send.md`        | 提供发送短信的服务                                                   |
+| `local-search`        | `references/local-search.md`        | 查询手机文档、笔记、日程、图库、yoyo记忆、钱包等                     |
+| `alarm`               | `references/alarm-create.md`        | 手机闹钟的创建                                                       |
+
+### Command and Parameters Construction Workflow
+
+Execute the following steps **in strict order** for each operation to construct parameter:
 
 ```
 ┌─────────────────────────────────────────────────────────────┐
 │  Step 1: INTENT RECOGNITION                                 │
-│  Parse user request → Identify target tool and operation    │
+│  Parse user request → Identify target tool to use           │
 └─────────────────────────────────────────────────────────────┘
                               ↓
 ┌─────────────────────────────────────────────────────────────┐
 │  Step 2: DOCUMENT CONSULTATION [MANDATORY]                  │
-│  Open references/*.md → Read tool definitions               │
+│  Open references/*.md → Read tool reference                 │
 │  ⚠️ PROHIBITED: Skip, guess, assume, or rely on memory      │
 └─────────────────────────────────────────────────────────────┘
                               ↓
 ┌─────────────────────────────────────────────────────────────┐
-│  Step 3: PARAMETER EXTRACTION                               │
-│  Extract: type, enum values, required/optional, defaults    │
-└─────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────┐
-│  Step 4: JSON CONSTRUCTION                                  │
-│  Build params object conforming to JSONSchema definiton     │
-└─────────────────────────────────────────────────────────────┘
-                              ↓
-┌─────────────────────────────────────────────────────────────┐
-│  Step 5: VALIDATION                                         │
+│  Step 3: PARAMETER EXTRACTION AND VALIDATION                │
 │  Verify: required fields present, enum case-sensitive match │
 └─────────────────────────────────────────────────────────────┘
 ```
 
-### Error Handling Protocol
+### Parameter Format Requirements
+
+- Parameters must be valid JSON
+- Enum values must match documentation exactly (case-sensitive)
+- Numeric values must be within defined ranges
+
+### Error Handling Protocolreference
 
-| Scenario                  | Required Action                                                                                                           |
-| ------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
-| **Ambiguous Request**     | User request unclear or missing required fields → Ask clarifying questions before proceeding                              |
-| **Unsupported Operation** | No matching tool definition found → Inform user: "Operation '[operation]' is not supported. Available operations: [list]" |
-| **Capability Mismatch**   | Selected node lacks required capability → Inform user and suggest alternative device or operation                         |
+| Scenario                  | Required Action                                                                                                          |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| **Ambiguous Request**     | User request unclear or missing required fields → Ask clarifying questions before proceeding                             |
+| **Unsupported Operation** | No matching tool reference found → Inform user: "Operation '[operation]' is not supported. Available operations: [list]" |
+| **Capability Mismatch**   | Selected node lacks required capability → Inform user and suggest alternative device or operation                        |
 
 ### ⚠️ Prohibited Actions
 
-- ❌ **DO NOT** construct parameters from memory or guesswork
+- ❌ **DO NOT** guess command names from user intent
 - ❌ **DO NOT** skip document consultation before executing commands
 - ❌ **DO NOT** use parameter values not defined in the documentation
+- ❌ **DO NOT** infer parameter structure from similar tools
+- ❌ **DO NOT** assume enum values without checking reference
+
+## Step 3. Invoke Node With Command and Parameters
 
-## Step 3. Invoke Node With Command And Params
+**Command**:
 
-**Command**: `openclaw nodes invoke --node <id|ip> --command <command> --params <json>`
+- window(CMD): `openclaw nodes invoke --node <ID|IP> --command <command> --params '<json>'`
+- Other: `openclaw nodes invoke --node <ID|IP> --command <command> --params "<json>"`
 
 **Purpose**: Send command to target node and initiate operation.
 
@@ -142,72 +169,35 @@ Execute the following steps **in strict order** for each operation:
 
 **Execute these validation steps in order. DO NOT skip any step.**
 
-| Step | Validation             | Action                                                 | On Failure                                                      |
-| ---- | ---------------------- | ------------------------------------------------------ | --------------------------------------------------------------- |
-| 1    | **Node Identifier**    | Extract `ID` or `IP` column from `nodes status` output | ❌ STOP: "Cannot use node name. Use ID or IP from nodes status" |
-| 2    | **Tool Documentation** | Read `references/<tool>.md` file completely            | ❌ STOP: "Tool documentation not found"                         |
-| 4    | **Command Name**       | Extract `command` exactly from tool documentation      | ❌ STOP: "Command mismatch. Check documentation"                |
-| 3    | **Required Params**    | Extract `params` from tool documentation               | ❌ STOP: "Missing required field: [field]"                      |
+| Step | Validation          | Action                                                 | On Failure                                                      |
+| ---- | ------------------- | ------------------------------------------------------ | --------------------------------------------------------------- |
+| 1    | **Node Identifier** | Extract `ID` or `IP` column from `nodes status` output | ❌ STOP: "Cannot use node name. Use ID or IP from nodes status" |
+| 2    | **Tool Reference**  | Read `references/<tool>.md` file completely            | ❌ STOP: "Tool reference not found"                             |
+| 4    | **Command Name**    | Extract `command` exactly from tool documentation      | ❌ STOP: "Command mismatch. Check documentation"                |
+| 3    | **Required Params** | Extract `params` from tool documentation               | ❌ STOP: "Missing required field: [field]"                      |
 
-#### Node Identifier Rules
+### Implementation differences between platforms
 
-```
-┌─────────────────────────────────────────────────────────────┐
-│  CORRECT: Use ID or IP from nodes status output             │
-│  ✅ openclaw nodes invoke 192.168.1.100 --command ...       │
-│  ✅ openclaw nodes invoke f5f8916028aa5 --command ...       │
-├─────────────────────────────────────────────────────────────┤
-│  INCORRECT: Use Node name column                            │
-│  ❌ openclaw nodes invoke "Honor Magic6" --command ...      │
-│  ❌ openclaw nodes invoke "My Phone" --command ...          │
-└─────────────────────────────────────────────────────────────┘
-```
+Due to the different shells parameter formats, it is necessary to **strictly** check the platform (not skippable). If it's Windows, the shell must use CMD.
 
-### Anti-Hallucination Rules
+**Platform-specific JSON parameter format:**
 
-**Before constructing ANY command, you MUST:**
-
-1. ✅ **READ** the tool documentation file completely
-2. ✅ **COPY** command name exactly from documentation
-3. ✅ **VERIFY** each parameter against JSONSchema
-4. ✅ **MATCH** enum values character-by-character
-
-**PROHIBITED actions that cause hallucination:**
-
-- ❌ **DO NOT** guess command names from user intent
-- ❌ **DO NOT** infer parameter structure from similar tools
-- ❌ **DO NOT** assume enum values without checking documentation
-- ❌ **DO NOT** use node names from the "Node" column in status output
-
-### Parameter Format Requirements
+| Platform    | Shell | Quote Style                     | Example                         |
+| ----------- | ----- | ------------------------------- | ------------------------------- |
+| **Windows** | CMD   | Double quotes, escape inner `"` | `"{\"actionType\":\"打电话\"}"` |
+| **Linux**   | Bash  | Single quotes                   | `'{"actionType":"打电话"}'`     |
+| **macOS**   | Bash  | Single quotes                   | `'{"actionType":"打电话"}'`     |
 
-| Platform                     | Format                                  | Example                 |
-| ---------------------------- | --------------------------------------- | ----------------------- |
-| **Bash (Linux/macOS)**       | Single quotes wrapping JSON             | `'{"level":50}'`        |
-| **Windows (PowerShell/CMD)** | Double quotes with escaped inner quotes | `"{\"level\":50}"`      |
-| **Complex Objects**          | Create JSON file first                  | `--params @params.json` |
-
-**Additional Requirements**:
-
-- Parameters must be valid JSON
-- Enum values must match documentation exactly (case-sensitive)
-- Numeric values must be within defined ranges
-
-### Examples
+**Windows CMD Execution:**
 
 ```bash
-# ✅ CORRECT: Execute volume control after consulting volume.md
-# Documentation: command = "volume.operate", params = { actionType: "增加" | "减少" | "关闭", level?: number }
-openclaw nodes invoke 192.168.1.100 --command volume.operate --params '{"actionType":"增加","level":50}'
-
-# ❌ INCORRECT: Using node name instead of ID/IP
-# openclaw nodes invoke "My Phone" --command volume.operate --params '{"actionType":"增加"}'
+openclaw nodes invoke <nodeId> --command phone.call --params "{\"actionType\":\"打电话\",\"phoneNumber\":\"10086\"}"
+```
 
-# ❌ INCORRECT: Wrong command name
-# openclaw nodes invoke <nodeId> --command volume --params '{"action":"up"}'
+**Linux/macOS Bash Execution:**
 
-# ❌ INCORRECT: Enum case mismatch
-# openclaw nodes invoke <nodeId> --command volume.operate --params '{"actionType":"UP"}'
+```bash
+openclaw nodes invoke <nodeId> --command phone.call --params '{"actionType":"打电话","phoneNumber":"10086"}'
 ```
 
 ### Error Handling
@@ -227,9 +217,9 @@ openclaw nodes invoke 192.168.1.100 --command volume.operate --params '{"actionT
 
 ```
 ┌─────────────────────────────────────────────────────────────┐
-│  RETRY FLOW (Max 3 attempts)                                │
+│  RETRY FLOW (Max 2 attempts)                                │
 ├─────────────────────────────────────────────────────────────┤
-│  Attempt 1 → FAIL → Wait 1s → Attempt 2 → FAIL → Wait 2s   │
+│  Attempt 1 → FAIL → Wait 1s → Attempt 2 → FAIL → Wait 1s   │
 │  → Attempt 3 → FAIL → STOP & REPORT ERROR                   │
 │                                                             │
 │  ⚠️ After 3 failed attempts:                                │
@@ -334,13 +324,3 @@ Would you like to check other nodes or retry later?"
 - ❌ **DO NOT** expose raw error codes to users
 - ❌ **DO NOT** assume user knows technical details
 - ❌ **DO NOT** leave user without next steps on failure
-
-## 快速参考命令
-
-```bash
-# 获取所有节点状态
-openclaw nodes status
-
-# 调用工具
-openclaw nodes invoke --node <id|name|ip> --command <command> --params <json>
-```