@honor-claw/yoyo 0.0.1-alpha.0

package/index.ts

@@ -0,0 +1,25 @@
+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 { setClawLogger } from "./src/utils/logger.js";
+
+const plugin = {
+  id: "yoyo",
+  name: "YOYOClaw",
+  description: "OpenClaw Honor Yoyo connection plugin",
+  configSchema: YoyoPluginConfigSchema,
+  register(api: OpenClawPluginApi) {
+    setYoyoRuntime(api.runtime);
+    setClawLogger(api.logger);
+
+    // 利用服务来管理核心连接任务进行~
+    api.registerService(ClawConnectionService);
+
+    // 注册所有的命令行
+    registerCommands(api);
+  },
+};
+
+export default plugin;

package/openclaw.plugin.json

@@ -0,0 +1,28 @@
+{
+  "id": "yoyo",
+  "skills": ["./skills"],
+  "configSchema": {
+    "type": "object",
+    "additionalProperties": false,
+    "properties": {
+      "user": {
+        "type": "object",
+        "properties": {
+          "token": {
+            "type": "string"
+          },
+          "expired": {
+            "type": "number"
+          },
+          "userId": {
+            "type": "string"
+          },
+          "userName": {
+            "type": "string"
+          }
+        },
+        "additionalProperties": false
+      }
+    }
+  }
+}

package/package.json

@@ -0,0 +1,59 @@
+{
+  "name": "@honor-claw/yoyo",
+  "version": "0.0.1-alpha.0",
+  "type": "module",
+  "description": "OpenClaw Honor Yoyo connection plugin",
+  "scripts": {
+    "test:unit": "vitest run",
+    "test:unit:watch": "vitest",
+    "test:coverage": "vitest run --coverage",
+    "ci:check": "npx tsc --noEmit && npm run test:coverage"
+  },
+  "license": "MIT",
+  "files": [
+    "index.ts",
+    "src/**/*.ts",
+    "!src/**/__tests__/**",
+    "!src/**/*.test.ts",
+    "skills",
+    "openclaw.plugin.json"
+  ],
+  "keywords": [
+    "openclaw",
+    "yoyo",
+    "ai",
+    "honor"
+  ],
+  "openclaw": {
+    "extensions": [
+      "./index.ts"
+    ]
+  },
+  "dependencies": {
+    "@sinclair/typebox": "0.34.48",
+    "http-proxy-agent": "^8.0.0",
+    "https-proxy-agent": "^8.0.0",
+    "jsonwebtoken": "^9.0.3",
+    "nanoid": "^5.1.6",
+    "open": "^11.0.0",
+    "registry-js": "^1.16.1",
+    "undici": "^7.3.0",
+    "uuid": "^13.0.0",
+    "ws": "^8.18.0",
+    "zod": "^4.3.6"
+  },
+  "devDependencies": {
+    "@types/jsonwebtoken": "^9.0.10",
+    "@types/node": "^25.0.10",
+    "@types/ws": "^8.5.13",
+    "@vitest/coverage-v8": "^2.1.8",
+    "commander": "^14.0.3",
+    "openclaw": "2026.3.8",
+    "tsx": "^4.21.0",
+    "typescript": "^5.7.0",
+    "vitest": "^2.1.8"
+  },
+  "peerDependencies": {
+    "openclaw": ">=2026.3.8"
+  }
+}

package/skills/yoyo-control/SKILL.md

@@ -0,0 +1,346 @@
+---
+name: yoyo-control
+version: 1.0.0
+description: Whenever a task requires **operating or controlling the phone**, eg. open app, send message, search contact, create schedule, phone calls, screen record, capture screenshot, volume, local search, etc.
+metadata: { "openclaw": { "emoji": "📱", "always": true } }
+---
+
+# Control phone with YOYO
+
+Follow the workflow to control phone or pad with YOYO, Don't guess the commands.
+
+## Workflow
+
+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.
+4. Present the result and confirm whether the operation was successful.
+
+### Step 1. Discover Nodes
+
+**Command**: `openclaw nodes status`
+
+**Purpose**: Retrieve current status of all nodes in the system to identify available devices ready to receive commands.
+
+**Execution result**:
+
+| Node       | ID       | IP       | Detail   | Status   | Caps   |
+| ---------- | -------- | -------- | -------- | -------- | ------ |
+| <nodeName> | <nodeId> | <nodeIP> | <detail> | <status> | <caps> |
+
+#### Capability Matching Logic
+
+Match device capabilities with user intent:
+
+```markdown
+1. Parse user intent → identify required capability keywords
+2. Check each node's `Caps` field for matching capabilities
+3. Filter nodes that support the required operation
+```
+
+#### Selection Rules
+
+**Automatic Selection** (single best match):
+
+- Only one node matches all required capabilities
+
+**User Confirmation Required** (multiple candidates):
+
+- Multiple nodes have similar capabilities
+- User specified device name is ambiguous
+- No clear capability distinction between candidates
+
+**No Match Handling**:
+
+- No connected nodes → Inform user: "No devices currently connected"
+- No capability match → Inform user: "No device supports [operation]. Available capabilities: [list]"
+- All nodes offline → Suggest: "Check device connectivity and try again"
+
+#### Pre-selection Checklist
+
+- ✅ Filter only `status: "connected"` nodes
+- ✅ Never attempt to control offline devices
+- ✅ Match node type and 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
+
+**⚠️ MANDATORY: Consult tool reference documentation 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.
+
+### 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:
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  Step 1: INTENT RECOGNITION                                 │
+│  Parse user request → Identify target tool and operation    │
+└─────────────────────────────────────────────────────────────┘
+                              ↓
+┌─────────────────────────────────────────────────────────────┐
+│  Step 2: DOCUMENT CONSULTATION [MANDATORY]                  │
+│  Open references/*.md → Read tool definitions               │
+│  ⚠️ 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                                         │
+│  Verify: required fields present, enum case-sensitive match │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### Error Handling Protocol
+
+| 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                         |
+
+### ⚠️ Prohibited Actions
+
+- ❌ **DO NOT** construct parameters from memory or guesswork
+- ❌ **DO NOT** skip document consultation before executing commands
+- ❌ **DO NOT** use parameter values not defined in the documentation
+
+## Step 3. Invoke Node With Command And Params
+
+**Command**: `openclaw nodes invoke --node <id|ip> --command <command> --params <json>`
+
+**Purpose**: Send command to target node and initiate operation.
+
+### ⚠️ MANDATORY Validation Steps
+
+**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]"                      |
+
+#### Node Identifier Rules
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  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 ...          │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### Anti-Hallucination Rules
+
+**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                     | 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
+
+```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":"增加"}'
+
+# ❌ INCORRECT: Wrong command name
+# openclaw nodes invoke <nodeId> --command volume --params '{"action":"up"}'
+
+# ❌ INCORRECT: Enum case mismatch
+# openclaw nodes invoke <nodeId> --command volume.operate --params '{"actionType":"UP"}'
+```
+
+### Error Handling
+
+**Maximum retry limit: 3 attempts. DO NOT exceed this limit to prevent infinite loops.**
+
+| Error Type             | Diagnosis                       | Resolution                                               | Retry? | Max Retries |
+| ---------------------- | ------------------------------- | -------------------------------------------------------- | ------ | ----------- |
+| **Invalid Parameters** | Check error message for details | Validate params against JSONSchema; fix parameter format | ✅ YES | 3           |
+| **Node Offline**       | Node not responding             | Re-verify node status with `openclaw nodes status`       | ❌ NO  | 0           |
+| **Permission Denied**  | Command not in allowlist        | Check `gateway.nodes.allowCommands` configuration        | ❌ NO  | 0           |
+| **Connection Error**   | Network or gateway issue        | Verify gateway running; check network connectivity       | ✅ YES | 3           |
+| **Timeout**            | Operation took too long         | Wait 2 seconds before retry                              | ✅ YES | 3           |
+| **Temporary Failure**  | Transient device error          | Wait 1 second before retry                               | ✅ YES | 3           |
+
+### Retry Protocol
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  RETRY FLOW (Max 3 attempts)                                │
+├─────────────────────────────────────────────────────────────┤
+│  Attempt 1 → FAIL → Wait 1s → Attempt 2 → FAIL → Wait 2s   │
+│  → Attempt 3 → FAIL → STOP & REPORT ERROR                   │
+│                                                             │
+│  ⚠️ After 3 failed attempts:                                │
+│  - DO NOT retry again                                       │
+│  - Report error to user with diagnosis                      │
+│  - Suggest manual intervention                              │
+└─────────────────────────────────────────────────────────────┘
+```
+
+## Step 4. Report Results
+
+**Purpose**: Present operation results to user with clear confirmation or error explanation.
+
+### Response Structure
+
+| Component                  | Success Case          | Failure Case       |
+| -------------------------- | --------------------- | ------------------ |
+| **Operation Confirmation** | What was executed     | What was attempted |
+| **State Change**           | Before → After values | Expected vs Actual |
+| **Key Information**        | Relevant details      | Error diagnosis    |
+| **Next Steps**             | Optional suggestions  | Required actions   |
+
+### Response Tone Guidelines
+
+| Scenario         | Tone                    | Detail Level             |
+| ---------------- | ----------------------- | ------------------------ |
+| Simple Success   | Concise, factual        | Brief confirmation       |
+| Complex Success  | Informative, structured | Detailed state changes   |
+| Partial Failure  | Helpful, diagnostic     | Error + recovery options |
+| Complete Failure | Clear, actionable       | Root cause + next steps  |
+
+### Response Templates
+
+#### Simple Success
+
+```
+✅ [Operation] completed on [Device]
+
+Example: "Volume set to 50% on Honor Magic6 (was 30%)"
+```
+
+#### Complex Success
+
+```
+✅ [Operation] completed on [Device]
+
+Changes:
+- [Property 1]: [Before] → [After]
+- [Property 2]: [Before] → [After]
+
+Example:
+"Bluetooth settings updated on Honor Magic6:
+- Bluetooth: OFF → ON
+- Connected devices: AirPods Pro, Honor Band
+- Visibility: Visible for 2 minutes"
+```
+
+#### Failure with Guidance
+
+```
+❌ [Operation] failed on [Device]
+
+Reason: [Error diagnosis]
+Suggestion: [Recovery action]
+
+Example:
+"Unable to control device - Honor Magic6 is offline (last seen 15 minutes ago).
+The device may need manual power-on or has lost network connection.
+Would you like to check other nodes or retry later?"
+```
+
+### Response Flow
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│  Parse command result                                       │
+└─────────────────────────────────────────────────────────────┘
+                              ↓
+┌─────────────────────────────────────────────────────────────┐
+│  Check result.success                                       │
+│  - true  → Build success response                           │
+│  - false → Build failure response with error details        │
+└─────────────────────────────────────────────────────────────┘
+                              ↓
+┌─────────────────────────────────────────────────────────────┐
+│  Format response based on operation complexity              │
+│  - Simple: Single line confirmation                         │
+│  - Complex: Structured list with state changes              │
+└─────────────────────────────────────────────────────────────┘
+                              ↓
+┌─────────────────────────────────────────────────────────────┐
+│  Present to user with appropriate tone                      │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### Best Practices
+
+- ✅ **DO** include device name in response for clarity
+- ✅ **DO** show before/after values when applicable
+- ✅ **DO** provide actionable suggestions on failure
+- ✅ **DO** ask before attempting alternative actions
+- ❌ **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>
+```

package/skills/yoyo-control/references/capture-screenshot.md

@@ -0,0 +1,66 @@
+# capture_screenshot 截屏工具使用说明
+
+## Tool Command
+
+```bash
+capture.shot
+```
+
+## Tool Parameters and Examples
+
+```json
+{
+  "name": "capture_screenshot",
+  "description": "该工具提供对截屏功能(将当前手机屏幕内容以图片的形式保存)的管理与触发能力，支持截屏和滚动截屏等操作。",
+  "parameters": {
+    "actionType": {
+      "type": "string",
+      "enum": ["截屏", "滚动截屏"],
+      "description": "截屏相关操作的动作类型，用于明确本次指令的主要行为。当需要对当前屏幕内容进行一次性截图保存时使用截屏；当需要对可上下滚动的长页面内容进行连续截图并合成为长图时使用滚动截屏。"
+    },
+    "app": {
+      "type": "string",
+      "description": "指定需要进行截屏操作的应用名称。当明确要求对某个特定应用界面进行截图时填写，用于限定截屏作用范围。"
+    }
+  },
+  "required": [],
+  "examples": [
+    {
+      "query": "截屏",
+      "arguments": {
+        "actionType": "截屏"
+      }
+    },
+    {
+      "query": "滚动截屏",
+      "arguments": {
+        "actionType": "滚动截屏"
+      }
+    },
+    {
+      "query": "立刻保存手机屏幕",
+      "arguments": {
+        "actionType": "截屏"
+      }
+    },
+    {
+      "query": "我想要滚动截屏",
+      "arguments": {
+        "actionType": "滚动截屏"
+      }
+    },
+    {
+      "query": "请将屏幕内容保存为图片",
+      "arguments": {
+        "actionType": "截屏"
+      }
+    },
+    {
+      "query": "我需要当前手机屏幕的图片",
+      "arguments": {
+        "actionType": "截屏"
+      }
+    }
+  ]
+}
+```

package/skills/yoyo-control/references/local-search.md

@@ -0,0 +1,27 @@
+# local_search 本地搜索工具使用说明
+
+## Tool Command
+
+```bash
+local.search
+```
+
+## Tool Parameters and Examples
+
+```json
+{
+  "name": "local_search",
+  "description": "用户手机内容RAG系统，用户使用自然语言，统一查询本地数据, 信源包括（文档、笔记、日程、图库、yoyo记忆、钱包），用于直接回答用户问题或生成概览性内容。\n【数据范围】\n- 本地数据：\n - 文档：本地存储的文档（如 Word、PDF、PPT 等），通过文本抽取和向量化建立索引。\n - 笔记：便签、备忘录、记事类应用中的文本内容。\n - 日程：日历和日程条目（会议、活动、提醒等），含时间、地点、参与人等结构化信息。",
+  "parameters": {
+    "query": {
+      "type": "string",
+      "description": "用户原始query，不需要进行任何改写"
+    },
+    "isSearchImage": {
+      "type": "boolean",
+      "description": "是否搜索图片"
+    }
+  },
+  "required": []
+}
+```

package/skills/yoyo-control/references/open-app.md

@@ -0,0 +1,54 @@
+# open_app 打开应用工具使用说明
+
+## Tool Command
+
+```bash
+app.open
+```
+
+## Tool Parameters and Examples
+
+```json
+{
+  "name": "open_app",
+  "description": "该工具用于帮助用户打开指定的 APP 应用，且不涉及任何具体 App 内部操作。",
+  "parameters": {
+    "app": {
+      "description": "需要打开的应用名称，若用户指定具体应用，则填写应用名称，若用户明确表示“所有应用”，则参数值为 all",
+      "type": "string"
+    },
+    "pkgName": {
+      "description": "应用包名",
+      "type": "string"
+    },
+    "app_description": {
+      "description": "类型描述。对 app 的补充描述，无论是否为空，都可以有这个参数，当且仅当 app 为空时才调用 description。示例：办公应用、聊天软件、音乐类应用。",
+      "type": "string"
+    }
+  },
+  "required": [],
+  "examples": [
+    {
+      "query": "打开小红书",
+      "arguments": {
+        "app": "网易云音乐",
+        "pkgName": "com.xingin.xhs"
+      }
+    },
+    {
+      "query": "打开淘宝",
+      "arguments": {
+        "app": "微信",
+        "pkgName": "com.taobao.taobao"
+      }
+    },
+    {
+      "query": "打开生活类软件",
+      "arguments": {
+        "app": "支付宝",
+        "app_description": "生活"
+      }
+    }
+  ]
+}
+```