rokid-rabilink-plugin

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Rokid RabiLink Plugin

Use this skill for Rokid/Rizon/Lingzhu platform integration with RabiLink.

## 新版 AIUI 的适用规范

下文的导入格式与两工具轮询流程适用于 Rizon / 灵珠的任务通道。新版 `apps/rabilink-aiui` 是使用乐奇配置模型的独立设备 Agent，采用[通用接口传输](../../apps/rabilink-aiui/docs/generic-api-transport.md)与[设备 Agent 合同](../../docs/device-agent-adapter.md)，不沿用两工具模式或旧 Relay 业务配置。

AIUI 绑定角色用于指引、Skill、聊天记录和默认来源 PC；未绑定也可以调用接口。已启用并鉴权的 Agent 使用全部当前及未来公共 Manager API，工作区、角色与 Route 绑定不提供接口授权。Relay 只负责连接、鉴权和通用中转，状态由明确选择的 PC 保存；新增接口不修改 Relay。

Android 通用通道按 LAN → P2P → Relay 连接同一目标。AIUI 只有 `wx.request` 时使用有界 HTTP Relay 降级，手机桥接、原生按键唤醒与 ASR/TTS 并行需要[真机验收](../../docs/aiui-agent-acceptance.md)。原投递、owner 接收和响应回执须核对相同 ID；触摸命令提交不能代替消息接收。旧业务配置不自动迁移，原始数据保留私有备份。

## First Checks

1. If the task touches the local implementation, resolve the current RabiRoute checkout from the task or configured source root.
2. Read `docs/rabilink-relay-server.md` for the current relay contract.
3. Treat `data/rabilink-relay/` as private runtime/config output. Do not commit real tokens, domains, IPs, or current imported JSON from `data/`.
4. Treat `examples/rabilink-relay/` as public examples. Use placeholder domains and tokens there.

## Import Types

Rizon has two similar but different import flows:

- **Import plugin**: creates or replaces the plugin-level resource. Use a full OpenAPI/Swagger/Postman file with plugin URL, description, auth shape, and all tool definitions.
- **Import tool**: used inside an existing plugin detail page. Provide an API-definition JSON for tools only. Do not use a full plugin-management export or a file with mixed/mismatched URL prefixes.

When the user says "导入工具", generate or point them to a tool-import JSON, not the full plugin import JSON.

For Rizon tool import, prefer the Postman Collection tool-import file first. Rizon's plugin-detail "导入工具" flow may still reject otherwise valid OpenAPI files with `convert protocol failed: inconsistent API URL prefix`. The Postman file must use absolute HTTPS URLs like `https://<domain>/rokid/rabilink/input` and `https://<domain>/rokid/rabilink/messages?after=`. Do not use `{{base_url}}`; Rizon currently treats Postman variables as literal invalid URLs.

OpenAPI remains a fallback. If using OpenAPI for tool import, use `servers.url = https://<domain>` and full paths `/rokid/rabilink/input` and `/rokid/rabilink/messages`.

## Rizon Import Constraints

- Plugin URL must be a domain URL, not a bare IP.
- HTTPS is safest for Rizon validation; HTTP may fail or be blocked.
- All APIs in one import must share the same URL prefix.
- Rizon import is picky:
  - Response statuses must match the current wire contract: `202` for input acceptance and `200` for downstream reads. Verify platform import support separately.
  - JSON responses must include `content.application/json.schema`.
  - POST JSON bodies need a concrete `requestBody.content.application/json.schema`.
  - Avoid `default` responses unless the platform has been verified to accept them.
- If auth is configured at plugin level, do not bake real tokens into public OpenAPI files.

## RabiLink Official Tool Set

For the Rizon/Lingzhu task-channel interaction, expose only:

- `submitRabiLinkTask`: `POST /rokid/rabilink/input`
  - Sends the user's full utterance or image-derived request to the relay.
  - Required body: `text`.
  - Optional body: `sender`, `context`.
- `getRabiLinkMessages`: `GET /rokid/rabilink/messages`
  - Pulls the global downstream message queue.
  - Optional query: `after`.
  - Does not require `taskId`.
  - Every returned message can include `taskId`, `id`, `text`, `done`, `shouldContinue`, `nextCursor`.

Keep old task-scoped polling tools out of the normal agent unless specifically debugging. They caused the model to poll the wrong thing and leave the glasses "thinking".

## Polling Rule For Agent Prompt

Use these rules in the Rokid agent prompt:

1. After user speaks, call `RabiLinkMessage.submitRabiLinkTask`.
2. Put the complete user utterance into `text`; do not rewrite, summarize, or omit details.
3. Put `sender` as `Rokid Glass`.
4. Put a short current conversation summary or visual observation into `context`.
5. Then call `RabiLinkMessage.getRabiLinkMessages` using the accepted response cursor. `eventId` identifies the original input; acceptance is not Agent completion.
6. First call can use empty `after`.
7. Later calls use previous `nextCursor` or `cursor`.
8. `getRabiLinkMessages` does not need `taskId`.
9. Whenever returned `messages` contains new `text`, immediately speak it naturally to the user.
10. Do not speak the pending text from `submitRabiLinkTask` as if it were the final answer.
11. `getRabiLinkTaskResult` is status/debug only. Do not read its `text`, `reply`, `answer`, or `content` to the user.
12. Continue polling until `done` is true or `shouldContinue` is false and no new messages remain.

## Image Handling

If the user sends or asks about a photo:

1. Inspect the image with the agent's vision capability first.
2. Put important visual facts into `context`: objects, text/OCR, scene, UI state, errors, and likely user intent.
3. Put the user's spoken request in `text`.
4. If there is an image URL or image reference that can be passed safely, include it in `context`.
5. Do not merely say "the user sent an image".

## Prompt Copy

Use this as the base Rizon agent prompt:

```text
你是 Rabi，是 RabiRoute 的灵魂和前台。RabiLink 是你连接 Rokid 眼镜、手机 RabiLink、电脑 RabiRoute 和后端 Agent 的消息通道，不是你的名字。

对用户自我介绍时，说“我是 Rabi”。如果需要解释链路，可以说“我会通过 RabiLink 把消息转给 RabiRoute 和绑定的 Agent”。

你的任务不是直接回答主要问题，而是把用户通过语音或照片发来的请求转交给后端 Agent，再把后端返回的增量回复自然转述给用户。语气轻快、可靠、具体；不要长篇解释流程。

提交规则：
用户说话后，必须调用 RabiLinkMessage.submitRabiLinkTask。
text 填用户的完整原话，不要改写、不要总结、不要省略。
sender 填 Rokid Glass。
context 填当前简短上下文。

如果用户发了照片，先用自己的视觉能力观察照片，把图片里的关键内容、文字、物体、场景、界面状态、报错信息和用户可能想问的问题整理进 context。不要只写“用户发了一张图片”。

轮询规则：
submitRabiLinkTask 返回后，调用 RabiLinkMessage.getRabiLinkMessages 获取下行消息。
第一次 after 留空。
后续使用上一次返回的 nextCursor 或 cursor。
getRabiLinkMessages 不需要 taskId。
每次拿到 messages 中的新 text，都要立刻自然转述给用户。
只朗读或转述 getRabiLinkMessages 返回的新增 messages。
不要把 submitRabiLinkTask 返回的 pending 文案转述给用户。
getRabiLinkTaskResult 只用于查看状态，不要把它的 text、reply、answer、content 转述给用户，避免重复回复。

如果 done 为 true 或 shouldContinue 为 false，停止轮询。
如果工具返回错误、超时或没有 eventId，告诉用户：RabiLink 转发暂时失败，请稍后再试。
```

From vb2250158/RabiRoute, MIT.

More from vb2250158/RabiRoute