@dhf-openclaw/grix 0.4.8 → 0.4.9

package/README.md

@@ -13,7 +13,7 @@ Its runtime remains focused on channel responsibilities:
 - send replies, media, and streaming chunks
 - support native channel actions such as `unsend` / `delete`
 
-The npm package also bundles OpenClaw skills for first-time setup and native channel actions, so users can install the plugin and complete Grix onboarding directly in conversation.
+The npm package also bundles OpenClaw skills for channel helpers and native channel actions.
 
 For full group-governance and API-agent admin capability, OpenClaw also needs the separate typed admin plugin:
 
@@ -23,7 +23,7 @@ If you are reading the admin plugin documentation first, also read the companion
 
 ## Which Package Do I Need?
 
-- Install only `@dhf-openclaw/grix` when you only need Grix channel transport and the bundled onboarding skill
+- Install only `@dhf-openclaw/grix` when you only need Grix channel transport and bundled helper skills
 - Install both `@dhf-openclaw/grix` and `@dhf-openclaw/grix-admin` when you want OpenClaw agents to use typed group governance or API-agent admin tools
 - Never install only `@dhf-openclaw/grix-admin` without configuring `@dhf-openclaw/grix` first, because the admin plugin reads credentials from `channels.grix`
 
@@ -91,20 +91,17 @@ If you need the detailed admin-side requirements, see the companion Grix admin p
 
 After install, OpenClaw can surface these bundled skills from this plugin:
 
-- `grix-auth-access`: inspect current readiness, follow the protocol-based main-agent path, create or reuse `provider_type=3` API agents when an access token is already available, install or enable `@dhf-openclaw/grix-admin`, and configure the main `channels.grix` path plus required tools
-- `egg-install`: handle Shrimp Pond egg install chats, confirm targets with the user in the current private conversation, execute persona.zip or skill.zip installation with正规步骤, and report progress or failures in normal dialogue
 - `message-send`: send current-session or cross-session Grix messages
 - `message-unsend`: unsend previously sent Grix messages
 
+`egg-install` is bundled in `@dhf-openclaw/grix-admin` so install the admin plugin when you need Shrimp Pond install workflow.
+
 You can confirm the bundled skill is visible with:
 
 ```bash
 openclaw skills list
-openclaw skills info grix-auth-access
 ```
 
-If the local main channel is already ready, `grix-auth-access` tells the user to log in to [https://grix.dhf.pub/](https://grix.dhf.pub/) directly. If group-governance prerequisites are still missing, the skill can continue by installing `@dhf-openclaw/grix-admin` and enabling the required tools block in chat.
-
 ## Configure
 
 ### `openclaw onboard`
@@ -296,19 +293,6 @@ The channel plugin exposes only channel-native message actions:
 - `unsend`
 - `delete`
 
-## Bundled Onboarding Skill
-
-Grix fully adapts the OpenClaw communication protocol, so OpenClaw interaction and Grix agent communication are directly connected. The bundled `grix-auth-access` skill is intended to explain that model to the user and complete the onboarding path:
-
-1. inspect whether the local OpenClaw main agent is already configured
-2. if the main channel is already configured, tell the user they can log in to [https://grix.dhf.pub/](https://grix.dhf.pub/) immediately
-3. otherwise continue with the protocol-based agent setup path
-4. create or reuse a `provider_type=3` API agent
-5. install or enable `@dhf-openclaw/grix-admin` when group-governance capability is requested
-6. configure the OpenClaw main `channels.grix` entry and required tools block
-
-This gives users a direct “install plugin, enable it, then finish setup in conversation” path. For full multi-agent groups, private chat, and group governance inside OpenClaw, the final local state must include both plugins plus the required tools block.
-
 ## Environment Variables
 
 - `GRIX_WS_URL`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dhf-openclaw/grix",
-  "version": "0.4.8",
+  "version": "0.4.9",
   "description": "Connect OpenClaw to grix.dhf.pub for OpenClaw website management with mobile PWA support",
   "type": "module",
   "main": "./dist/index.js",
@@ -28,11 +28,6 @@
     "README.md",
     "openclaw.plugin.json",
     "dist/index.js",
-    "skills/grix-auth-access/SKILL.md",
-    "skills/grix-auth-access/agents/openai.yaml",
-    "skills/grix-auth-access/references",
-    "skills/grix-auth-access/scripts/grix_auth.py",
-    "skills/egg-install/SKILL.md",
     "skills/message-send/SKILL.md",
     "skills/message-unsend/SKILL.md",
     "skills/message-unsend/flowchart.mermaid"

package/skills/egg-install/SKILL.md

@@ -1,149 +0,0 @@
----
-name: egg-install
-description: 在虾塘触发的安装私聊中处理 egg 安装。适用于主 OpenClaw agent 收到包含 install_id、egg、install、main_agent 的安装上下文时，负责与用户多轮确认、执行 persona.zip 到 OpenClaw agent 或 skill.zip 到 Claude agent 的正规安装流程，并在当前私聊里持续回报进度、失败原因和最终结果。
----
-
-# Egg Install
-
-仅在"虾塘发起的安装私聊"里使用这个技能。
-
-这类会话通常会先收到一条系统代发的安装请求，正文里会带一个 JSON 上下文块，至少包含：
-
-- `install_id` — 安装单唯一 ID，所有状态指令必须使用原值
-- `egg` — egg 包标识，格式为 `<name>@<version>` 或带完整下载 URL 的对象
-- `install` — 安装模式，枚举值：`create_new`（新建目标 agent）或 `existing_agent`（安装到已有 agent）
-- `main_agent` — 发起安装的主 OpenClaw agent ID，安装完成后如需通知或回调，使用该 ID
-
-你的职责不是返回隐藏协议结果，而是直接在当前私聊里把安装流程做完。
-
-## 工作方式
-
-1. 先读完整个 JSON 上下文，确认 egg、版本、安装模式和目标类型。
-2. 在真正动手前，先在当前私聊里和用户确认关键目标。
-3. `create_new` 时，先确认新 agent 的命名和用途，再继续创建。
-4. `existing_agent` 时，只能操作上下文里指定的目标 agent，不要私自换目标。
-5. 安装过程中，每完成一个关键动作就用自然语言回报一次进度。
-6. 在"包下载完成"和"安装内容落位完成待校验"两个节点，各额外发送一条 `status=running` 的**独立安装状态指令消息**。
-7. 最终成功或失败时，必须发送一条 `status=success` 或 `status=failed` 的**独立安装状态指令消息**。
-8. 出错时，直接说明失败点、影响和下一步建议，不要模糊带过。
-9. 最终明确告诉用户：装到了哪个 agent、结果成功还是失败、后续是否还要继续操作。
-
-## 绝对规则
-
-- 只在当前私聊里沟通，不要切换到隐藏协议，不要输出机器专用 JSON。
-- 必须按 OpenClaw / Claude 的正规步骤安装，不要直接改后端数据库。
-- 需要创建远端 API agent 时，使用 `grix_agent_admin`。
-- `persona.zip` 只能面向 OpenClaw 目标。
-- `skill.zip` 只能面向 Claude 目标。
-- 不要自动新建 Claude 目标 agent。
-- 没完成校验前，绝不能宣称安装成功。
-- 如果新建目标后又失败了，能安全回滚就先回滚；不能回滚就如实告诉用户当前残留状态。
-- 最终成功或失败时，必须发送一条独立的 `egg-install-status` 指令消息。
-- 状态指令消息必须单独发送，不要和自然语言解释混在同一条里。
-- 用户拒绝确认或主动取消时，必须发送 `status=failed`、`error_code=user_cancelled` 的状态指令后再结束。
-
-## 安装状态指令
-
-server 不会猜自然语言。要让安装单进入"进行中 / 成功 / 失败"，你必须发送这类单行消息：
-
-```text
-[[egg-install-status|install_id=<INSTALL_ID>|status=<running|success|failed>|step=<STEP>|summary=<URI_ENCODED_SUMMARY>]]
-```
-
-常用可选字段：
-
-- `target_agent_id=<AGENT_ID>`：成功时尽量带上，尤其是 `create_new`。
-- `detail_text=<URI_ENCODED_DETAIL>`：补充更长说明。
-- `error_code=<ERROR_CODE>`：失败时建议带上。
-- `error_msg=<URI_ENCODED_ERROR_MSG>`：失败时建议带上。
-
-规则：
-
-1. `install_id` 必须使用上下文里的原值。
-2. `status` 只能是 `running`、`success`、`failed`。
-3. `summary`、`detail_text`、`error_msg` 如果有空格、中文或特殊字符，按 URI component 编码。
-4. 这条指令只负责状态收口；如果要跟用户解释原因，另发一条正常文字消息。
-5. `create_new` 成功时，必须尽量带 `target_agent_id`，否则 server 可能无法通过最终校验。
-
-## 推荐流程
-
-### `persona.zip` -> OpenClaw
-
-1. 读取上下文，确认是 `create_new` 还是 `existing_agent`。
-2. 和用户确认目标 agent 或新 agent 命名；**用户拒绝则发 `failed/user_cancelled` 指令后结束**。
-3. 如果需要新建远端 API agent，用 `grix_agent_admin` 创建。
-4. 用 OpenClaw 正规步骤准备本地目标目录和配置。
-5. 下载 egg 包，并校验 hash / manifest（如果上下文提供）。
-6. 发送 `status=running`、`step=downloaded` 状态指令。
-7. 安装 persona 内容。
-8. 发送 `status=running`、`step=installed` 状态指令。
-9. 按需刷新或重启本地运行时。
-10. 校验目标 agent 仍然可用。
-    - 校验失败 → 尝试回滚（含步骤3新建的远端 agent），无法回滚则如实告知残留状态 → 发 `failed` 指令后结束。
-11. 发送 `status=success` 状态指令（带 `target_agent_id`），再向用户汇报完成。
-
-### `skill.zip` -> Claude
-
-1. 确认上下文指定的 Claude 目标 agent 存在；**不存在则发 `failed/target_not_found` 指令后结束**。
-2. 和用户确认目标 agent；**用户拒绝则发 `failed/user_cancelled` 指令后结束**。
-3. 下载 skill 包，并校验 hash / manifest（如果上下文提供）。
-4. 发送 `status=running`、`step=downloaded` 状态指令。
-5. 用 Claude 正规步骤安装 skill 包。
-6. 发送 `status=running`、`step=installed` 状态指令。
-7. 按需刷新配置或重载运行时。
-8. 校验目标 agent 仍然可用。
-    - 校验失败 → 如实告知用户 → 发 `failed` 指令后结束。
-9. 发送 `status=success` 状态指令（带 `target_agent_id`），再向用户汇报完成。
-
-## 每次安装至少校验这些点
-
-- 目标 agent 选对了
-- 包已成功下载
-- hash / manifest 校验通过（如果提供）
-- 安装内容已经落到目标位置
-- 目标 agent 安装后仍然可用
-
-## 指令示例
-
-进行中（下载完成）：
-
-```text
-[[egg-install-status|install_id=eggins_20370001|status=running|step=downloaded|summary=%E5%B7%B2%E4%B8%8B%E8%BD%BD%E5%B9%B6%E9%AA%8C%E8%AF%81%E5%AE%89%E8%A3%85%E5%8C%85]]
-```
-
-进行中（安装落位完成）：
-
-```text
-[[egg-install-status|install_id=eggins_20370001|status=running|step=installed|summary=%E5%AE%89%E8%A3%85%E5%86%85%E5%AE%B9%E5%B7%B2%E8%90%BD%E4%BD%8D%EF%BC%8C%E6%A0%A1%E9%AA%8C%E4%B8%AD]]
-```
-
-成功：
-
-```text
-[[egg-install-status|install_id=eggins_20370001|status=success|step=completed|target_agent_id=2035123456789012345|summary=%E5%B7%B2%E5%AE%8C%E6%88%90%E5%AE%89%E8%A3%85]]
-```
-
-失败（用户取消）：
-
-```text
-[[egg-install-status|install_id=eggins_20370001|status=failed|step=user_cancelled|error_code=user_cancelled|summary=%E7%94%A8%E6%88%B7%E5%8F%96%E6%B6%88%E5%AE%89%E8%A3%85]]
-```
-
-失败（目标不存在）：
-
-```text
-[[egg-install-status|install_id=eggins_20370001|status=failed|step=target_not_found|error_code=target_not_found|error_msg=%E6%8C%87%E5%AE%9A%E7%9A%84%20Claude%20agent%20%E4%B8%8D%E5%AD%98%E5%9C%A8|summary=%E5%AE%89%E8%A3%85%E5%A4%B1%E8%B4%A5]]
-```
-
-失败（下载失败）：
-
-```text
-[[egg-install-status|install_id=eggins_20370001|status=failed|step=download_failed|error_code=download_failed|error_msg=%E4%B8%8B%E8%BD%BD%E5%AE%89%E8%A3%85%E5%8C%85%E5%A4%B1%E8%B4%A5|summary=%E5%AE%89%E8%A3%85%E5%A4%B1%E8%B4%A5]]
-```
-
-## 回复风格
-
-- 用正常对话回复用户
-- 进度回报要短、明确、可执行
-- 失败说明要具体
-- 最终总结必须包含目标 agent 和安装结果

package/skills/grix-auth-access/SKILL.md

@@ -1,173 +0,0 @@
----
-name: grix-auth-access
-description: 用 Grix 协议创建或复用 `provider_type=3` 的 Agent API 类型 agent，并按 `@dhf-openclaw/grix` 与 `@dhf-openclaw/grix-admin` 说明为 OpenClaw 主 agent 配置 grix 渠道和群管理能力。插件接入目标是让用户在 `https://grix.dhf.pub/` 管理 OpenClaw，并支持移动端 PWA 页面。
----
-
-# Grix Auth Access
-
-Use the bundled scripts and local OpenClaw CLI to bootstrap Grix channel access for the main OpenClaw agent.
-
-## Business Capabilities
-
-1. `create-api-agent`
-2. `inspect@dhf-openclaw`
-3. `configure@dhf-openclaw`
-4. `bootstrap@dhf-openclaw`
-
-## Explain Grix
-
-When the user asks what Grix is, what they gain after setup, or whether it is worth configuring, explain it with these points:
-
-1. Start by saying this plugin is connected so the user can manage OpenClaw on `https://grix.dhf.pub/`, with mobile PWA page support.
-2. Grix fully adapts the OpenClaw communication protocol, so OpenClaw interaction and channel transport are natively connected.
-3. It supports multi-agent group chat, agent private chat, and agent-to-agent communication in one connected path.
-4. Setup is simple: hand this skill to OpenClaw, Claude, or Codex, and it can inspect the current state, stop if everything is already ready, or finish the bootstrap flow, including `@dhf-openclaw/grix-admin` and the required tools block.
-5. If the result says `portal_ready=true`, tell the user they can log in to `https://grix.dhf.pub/` directly and start using it.
-6. Prefer the returned `user_reply_templates.recommended_message` when you want a concise user-facing answer.
-
-## Fast Path
-
-If the user wants the main OpenClaw agent to gain Grix channel ability quickly:
-
-1. If the request is first to verify whether the local machine is already ready, run `inspect@dhf-openclaw` before any local mutation.
-2. If `inspect@dhf-openclaw` returns `inspection_state=already_configured` and the user did not ask to bind a different Grix account or agent, stop there and tell the user to log in to `https://grix.dhf.pub/` directly.
-3. If `ready_for_main_agent=true` but `ready_for_group_governance=false`, tell the user the website is already usable, and only continue if they want full OpenClaw group-management capability.
-4. Otherwise prefer `bootstrap@dhf-openclaw`.
-5. Reuse an existing same-name `provider_type=3` agent when possible; rotate its API key to get a fresh usable `api_key`.
-6. If no matching API agent exists, create one.
-7. Inspect local OpenClaw plugin state, main `channels.grix` target state, `grix-admin` state, and `tools` state before planning any local mutation.
-8. Return the smallest necessary OpenClaw apply plan, plus `onboard_values`, environment variables, and the required `tools` block.
-9. Prepare or apply the OpenClaw plugin setup using both `@dhf-openclaw/grix` and `@dhf-openclaw/grix-admin`.
-
-## Workflow
-
-### A. Create provider_type=3 agent
-
-1. Start from the Grix protocol access path and use the provided `access_token`.
-2. Ask for `agent_name`.
-3. By default, prefer reusing an existing same-name `provider_type=3` agent:
-   - list existing agents
-   - if found, rotate API key and reuse it
-   - if not found, create a new agent
-4. Run `scripts/grix_auth.py create-api-agent --access-token ... --agent-name ...`.
-5. Return `agent_id`, `agent_name`, `provider_type`, `api_endpoint`, `api_key`, and `api_key_hint`.
-
-### B. Configure OpenClaw grix channel
-
-1. Require `agent_id`, `api_endpoint`, and `api_key`.
-2. Default channel name: `grix-main`.
-3. Treat this as the main OpenClaw agent setup path plus the local group-governance prerequisites.
-4. Prefer the README's direct-config style for the main agent:
-   - inspect `~/.openclaw/openclaw.json`
-   - update base `channels.grix.enabled/wsUrl/agentId/apiKey`
-   - when the user explicitly wants Grix chat exec approvals, also update `tools.exec`, `approvals.exec`, and `channels.grix.*.execApprovals`
-   - update `tools.profile`, `tools.alsoAllow`, and `tools.sessions.visibility`
-   - preserve other existing `grix` keys such as `accounts`, stream settings, and reconnect settings
-   - preserve unrelated existing `tools.alsoAllow` entries after the required ones
-5. Inspect plugin state through `openclaw plugins info grix --json` and `openclaw plugins info grix-admin --json`; only include the minimal plugin commands still needed.
-6. Use `scripts/grix_auth.py configure@dhf-openclaw ...` first without `--apply` to preview commands, setup state, and config diff when the user has not explicitly requested local mutation.
-7. Use `--apply` only when the user explicitly wants you to install/configure OpenClaw locally.
-8. Follow the plugin package instructions:
-   - `openclaw plugins install @dhf-openclaw/grix`
-   - `openclaw plugins enable grix`
-   - `openclaw plugins install @dhf-openclaw/grix-admin`
-   - `openclaw plugins enable grix-admin`
-   - `openclaw onboard` can also consume `wsUrl`, `agentId`, and `apiKey`
-   - channel config follows the README direct-config alternative for the main agent
-   - exec approval config follows the README `Exec Approvals` section when the user wants approvals in Grix chat
-   - only place approver ids under `channels.grix.execApprovals` or `channels.grix.accounts.<accountId>.execApprovals`
-   - never invent unsupported keys such as `approvals.exec.timeoutMs` or `approvals.exec.approvers`
-   - tools config must include:
-
-```json
-{
-  "tools": {
-    "profile": "coding",
-    "alsoAllow": [
-      "message",
-      "grix_group",
-      "grix_agent_admin"
-    ],
-    "sessions": {
-      "visibility": "agent"
-    }
-  }
-}
-```
-
-   - `openclaw gateway restart`
-
-### C. Inspect local OpenClaw readiness
-
-Use:
-
-```bash
-scripts/grix_auth.py inspect@dhf-openclaw
-```
-
-This action:
-
-1. checks whether the `grix` plugin is detected and loaded
-2. checks whether base `channels.grix` is present and internally consistent
-3. checks whether `grix-admin` is detected and loaded
-4. checks whether `tools.profile`, `tools.alsoAllow`, and `tools.sessions.visibility` match the required group-governance settings
-5. returns `inspection_state`, `ready_for_main_agent`, `ready_for_group_governance`, and `recommended_next_steps`
-6. if the main channel is already ready, return `portal_url`, `portal_ready=true`, and a direct "login to the website and try it" hint, even when local group governance is still pending
-7. never mutates local OpenClaw state
-
-### D. One-shot bootstrap
-
-Use:
-
-```bash
-scripts/grix_auth.py bootstrap@dhf-openclaw ...
-```
-
-This action can:
-
-1. use a provided `access_token`
-2. reuse-or-create the API agent
-3. generate OpenClaw setup preview for both plugins and the required tools config
-4. apply OpenClaw setup when `--apply` is present
-5. expose `bootstrap_state`, `channel_credentials`, `onboard_values`, environment variables, and required tools config that the next agent step can consume directly
-
-## Guardrails
-
-1. Do not invent tokens, agent IDs, or API keys.
-2. Treat `create-api-agent`, key rotation on reused agents, and `configure@dhf-openclaw --apply` as side-effecting operations.
-3. For local OpenClaw mutations, prefer preview first; only use `--apply` after explicit user intent to actually configure the local machine.
-4. Do not create duplicate same-name `provider_type=3` agents when a reusable one already exists.
-5. Keep API key output exact when the user asks for it.
-6. `provider_type` for created or reused Grix agent must be `3`.
-7. When configuring the main agent, prefer updating base `channels.grix` over inventing extra accounts.
-8. Treat `plugin_missing`, `plugin_not_ready`, `admin_plugin_missing`, `admin_plugin_not_ready`, `tools_not_ready`, and `needs_main_config_update` as distinct setup states; do not claim group-governance readiness unless both plugins are ready, base `channels.grix` matches the target, and the required tools block is active.
-9. In local-config previews, redact the currently stored OpenClaw `apiKey`; only return the newly created target `api_key` exactly.
-10. If `inspect@dhf-openclaw` says the main agent is already configured and the user did not ask for a different agent target, stop instead of continuing into setup mutation.
-
-## Script Contract
-
-Script: `scripts/grix_auth.py`
-
-Actions:
-
-1. `create-api-agent`
-2. `inspect@dhf-openclaw`
-3. `configure@dhf-openclaw`
-4. `bootstrap@dhf-openclaw`
-
-Success shape highlights:
-
-1. `create-api-agent` returns top-level `agent_id`, `api_endpoint`, `api_key`, `api_key_hint`, and whether the agent was reused or newly created
-2. `inspect@dhf-openclaw`, `configure@dhf-openclaw`, and `bootstrap@dhf-openclaw` can return `portal_url`, `portal_ready`, and `portal_hint`
-3. `inspect@dhf-openclaw`, `configure@dhf-openclaw`, and `bootstrap@dhf-openclaw` also return `grix_intro`, `grix_highlights`, and `user_reply_templates` so the agent can explain the concept to the user consistently
-4. `create-api-agent` returns the `provider_type=3` agent data
-5. `inspect@dhf-openclaw` returns `inspection_state`, `plugin_status`, `admin_plugin_status`, redacted current main grix config, current tools config, channel consistency checks, tools checks, readiness booleans, and `recommended_next_steps`
-6. `configure@dhf-openclaw` returns `setup_state`, `plugin_status`, `admin_plugin_status`, current and next main grix config, current and next tools config, minimal plugin commands, `onboard_values`, environment variables, required tools config, and `command_results` when `--apply` is used
-7. `bootstrap@dhf-openclaw` returns nested `created_agent`, `openclaw_setup`, top-level `channel_credentials`, and `bootstrap_state`
-
-## References
-
-1. Read [references/api-contract.md](references/api-contract.md) for API-agent creation routes.
-2. Read [references/openclaw-setup.md](references/openclaw-setup.md) for the `@dhf-openclaw/grix` + `@dhf-openclaw/grix-admin` setup flow.
-3. Read [references/grix-concepts.md](references/grix-concepts.md) when the user needs a clear product/concept explanation.
-4. Read [references/user-replies.md](references/user-replies.md) when the user needs short, direct pitch or status replies.

package/skills/grix-auth-access/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Grix Auth Access"
-  short_description: "Inspect, explain, or bootstrap Grix for OpenClaw."
-  default_prompt: "Use $grix-auth-access to explain what Grix is, inspect whether the local OpenClaw main agent already has a healthy grix channel plus the required grix-admin and tools setup, reuse the returned user_reply_templates when replying to the user, stop if everything is already configured and tell the user to log in to https://grix.dhf.pub/ directly, or otherwise follow the protocol-based main-agent path: reuse-or-create a provider_type=3 API agent, install or enable @dhf-openclaw/grix-admin only when needed, and return the minimal main-agent setup path including tools.alsoAllow for message, grix_group, and grix_agent_admin."

package/skills/grix-auth-access/references/api-contract.md

@@ -1,56 +0,0 @@
-# API Contract
-
-## Base
-
-1. Website: `https://grix.dhf.pub/`
-2. Public Grix API base: `https://grix.dhf.pub/v1`
-
-## Route Mapping
-
-### Agent bootstrap action
-
-| Action | Method | Route | Auth |
-|---|---|---|---|
-| `create-api-agent` | `POST` | `/agents/create` | `Authorization: Bearer <access_token>` |
-| `list-agents` (internal helper) | `GET` | `/agents/list` | `Authorization: Bearer <access_token>` |
-| `rotate-api-agent-key` (internal helper) | `POST` | `/agents/:id/api/key/rotate` | `Authorization: Bearer <access_token>` |
-
-## Payloads
-
-### `create-api-agent`
-
-```json
-{
-  "agent_name": "grix-main",
-  "provider_type": 3
-}
-```
-
-`provider_type=3` means Agent API type.
-
-## Reuse flow
-
-When the same-name `provider_type=3` agent already exists, the skill should:
-
-1. read `/agents/list`
-2. find the exact-name API agent
-3. rotate its key through `/agents/:id/api/key/rotate`
-4. reuse the returned `api_endpoint` and fresh `api_key`
-
-## Success Highlights
-
-### `create-api-agent`
-
-The bundled script lifts these fields to the top level:
-
-1. `agent_id`
-2. `agent_name`
-3. `provider_type`
-4. `api_endpoint`
-5. `api_key`
-6. `api_key_hint`
-7. `session_id`
-
-## Common Errors
-
-1. create-agent or rotate-key returns missing `api_endpoint` or `api_key`

package/skills/grix-auth-access/references/grix-concepts.md

@@ -1,30 +0,0 @@
-# Grix Concepts
-
-## Canonical Explanation
-
-这个插件接入是为了在 `https://grix.dhf.pub/` 网站管理 OpenClaw，并支持移动端 PWA 页面。Grix 完全适配 OpenClaw 的通讯协议，不是一层临时转接，而是把 OpenClaw 的渠道交互、agent 通信和运行时连接到同一条能力链路里。
-
-## Feature Highlights
-
-1. 支持多 agent 建群互聊
-2. 支持 agent 私聊
-3. agent 之间通信链路完美打通
-4. 接入目标是让你直接在 `https://grix.dhf.pub/` 管理 OpenClaw，移动端可用 PWA 页面
-5. 配置简单易用，只需要将这个技能交给 OpenClaw、Claude、Codex，即可完成检查与配置
-6. 如需 OpenClaw 内的群管理能力，还需要安装启用 `@dhf-openclaw/grix-admin`，并在 `tools` 中允许 `message`、`grix_group`、`grix_agent_admin`
-
-## Default User-Facing Framing
-
-### One sentence
-
-这个插件接入是为了在 `https://grix.dhf.pub/` 管理 OpenClaw，并支持移动端 PWA 页面。
-
-### Short paragraph
-
-这个插件把 OpenClaw 的渠道交互和 agent 通信直接接到 Grix，核心目标是让你在 `https://grix.dhf.pub/` 管理 OpenClaw，并在手机上通过 PWA 页面使用。除此之外，它也支持多 agent 建群互聊、agent 私聊和 agent 间互通。配置上尽量做到了简单，只要把这个技能交给 OpenClaw、Claude 或 Codex，就可以先检查现状，已经配置好就直接停下，否则继续按主 agent 协议路径完成配置；如果用户还要在 OpenClaw 里直接做群管理，还会继续补齐 `@dhf-openclaw/grix-admin` 和 required tools 配置。
-
-## After Setup
-
-1. If the result says `portal_ready=true`, tell the user to log in to `https://grix.dhf.pub/` directly to try it.
-2. If the local main agent is already configured, do not continue into redundant install, enable, or restart steps unless the user explicitly wants a different Grix agent target.
-3. If the main channel is already configured but local group governance is not, tell the user they can still log in to the website immediately and decide whether to continue the admin-plugin/tools setup.

package/skills/grix-auth-access/references/openclaw-setup.md

@@ -1,154 +0,0 @@
-# OpenClaw Setup
-
-This flow follows the current `@dhf-openclaw/grix` and `@dhf-openclaw/grix-admin` package README expectations.
-
-## Package
-
-1. Plugin package: `@dhf-openclaw/grix`
-2. Admin package: `@dhf-openclaw/grix-admin`
-3. Purpose: Grix channel transport plus typed group-governance capability for OpenClaw
-
-## Install and Enable
-
-```bash
-openclaw plugins install @dhf-openclaw/grix
-openclaw plugins enable grix
-openclaw plugins install @dhf-openclaw/grix-admin
-openclaw plugins enable grix-admin
-openclaw gateway restart
-```
-
-## Plugin Inspection
-
-```bash
-openclaw plugins info grix --json
-openclaw plugins info grix-admin --json
-```
-
-Use this to inspect whether both plugins are already present and loaded before planning local mutations.
-
-## Onboard Wizard
-
-Choose `Grix` in `openclaw onboard` channel setup and enter:
-
-1. `wsUrl`
-2. `agentId`
-3. `apiKey`
-
-## Channel Setup Command
-
-```bash
-openclaw channels add \
-  --channel grix \
-  --name grix-main \
-  --http-url 'wss://grix.dhf.pub/v1/agent-api/ws?agent_id=<YOUR_AGENT_ID>' \
-  --user-id '<YOUR_AGENT_ID>' \
-  --token '<YOUR_API_KEY>'
-```
-
-## Direct Config Alternative
-
-```json
-{
-  "channels": {
-    "grix": {
-      "enabled": true,
-      "wsUrl": "wss://grix.dhf.pub/v1/agent-api/ws?agent_id=<YOUR_AGENT_ID>",
-      "agentId": "<YOUR_AGENT_ID>",
-      "apiKey": "<YOUR_API_KEY>"
-    }
-  },
-  "tools": {
-    "profile": "coding",
-    "alsoAllow": [
-      "message",
-      "grix_group",
-      "grix_agent_admin"
-    ],
-    "sessions": {
-      "visibility": "agent"
-    }
-  }
-}
-```
-
-## Environment Variables
-
-```bash
-export GRIX_WS_URL='wss://grix.dhf.pub/v1/agent-api/ws?agent_id=<YOUR_AGENT_ID>'
-export GRIX_AGENT_ID='<YOUR_AGENT_ID>'
-export GRIX_API_KEY='<YOUR_API_KEY>'
-```
-
-## Practical Rules
-
-1. Start with a local readiness inspection when the task is "see whether the main OpenClaw agent is already ready"
-2. For the OpenClaw main agent, prefer the direct-config alternative over repeatedly adding named channel accounts
-3. Default channel name for preview commands: `grix-main`
-4. Inspect plugin state first and only keep the minimal remaining plugin commands in the apply plan
-5. Preview commands and config diff first unless the user clearly asked to apply them
-6. Only execute local OpenClaw mutations when the user wants the machine configured now
-7. After config update, restart the gateway
-8. Preserve other existing `channels.grix` fields such as `accounts`, `streamChunkChars`, `streamChunkDelayMs`, and `reconnectMs`
-9. Preserve unrelated existing `tools.alsoAllow` entries, but ensure `message`, `grix_group`, and `grix_agent_admin` are present and `tools.sessions.visibility=agent`
-10. Return `onboard_values` and `GRIX_*` environment variables together with the direct-config preview so downstream agents can reuse the same credentials without recomputing them
-11. If the main channel is already healthy, or setup has just been applied successfully, tell the user they can log in to `https://grix.dhf.pub/` directly to experience it
-12. Do not claim local group-governance readiness unless both plugins are loaded and the required tools block is active
-
-## Exec Approval Setup
-
-Grix chat exec approvals only require `@dhf-openclaw/grix`. They do not require `@dhf-openclaw/grix-admin`.
-
-Minimal OpenClaw config:
-
-```json
-{
-  "tools": {
-    "exec": {
-      "host": "gateway",
-      "security": "allowlist",
-      "ask": "always"
-    }
-  },
-  "approvals": {
-    "exec": {
-      "enabled": true,
-      "mode": "session"
-    }
-  },
-  "channels": {
-    "grix": {
-      "execApprovals": {
-        "enabled": true,
-        "approvers": ["<GRIX_SENDER_ID>"]
-      }
-    }
-  }
-}
-```
-
-If the deployment uses a named Grix account, move the approver config to `channels.grix.accounts.<accountId>.execApprovals`.
-
-Rules:
-
-1. `approvals.exec` currently supports only `enabled` and `mode`
-2. Do not add `approvals.exec.timeoutMs`
-3. Do not add `approvals.exec.approvers`
-4. Put approver ids only under `channels.grix.execApprovals` or `channels.grix.accounts.<accountId>.execApprovals`
-5. `approvers` must be Grix sender ids, not OpenClaw agent ids
-6. After config changes, run `openclaw gateway restart`
-
-Verification:
-
-```bash
-openclaw plugins info grix --json
-openclaw config get approvals.exec --json
-openclaw config get channels.grix --json
-```
-
-Expected result:
-
-1. `plugins info grix` shows `status=loaded`
-2. `approvals.exec` is `enabled=true` and `mode=session`
-3. the active Grix account shows `execApprovals.enabled=true`
-4. the active Grix account contains at least one sender id in `execApprovals.approvers`