@lansenger-pm/openclaw-lansenger-channel 2.8.1 → 2.8.3

package/README.fr.md

@@ -33,7 +33,7 @@ Connecte OpenClaw à Lansenger — une plateforme de messagerie d'entreprise —
 
 **Stratégie par défaut** : utiliser `formatText` en priorité pour les réponses Markdown. Revenir à `text` pour les pièces jointes. Les deux types supportent @mention via le paramètre `reminder` — inclure « @姓名 » dans le texte pour les mentions.
 
-## Outils de l'agent (v2.5.1)
+## Outils de l'agent
 
 | Outil | Description |
 |-------|-------------|
@@ -47,32 +47,29 @@ Connecte OpenClaw à Lansenger — une plateforme de messagerie d'entreprise —
 | `lansenger_revoke_message` | Révoquer un message précédemment envoyé |
 | `lansenger_query_groups` | Interroger les groupes disponibles |
 
-## Installation rapide
+## Installation et Configuration
 
-### Via OpenClaw CLI (recommandé)
+### Flux recommandé en 4 étapes
 
 ```bash
-# 1. Install the plugin
+# 1. Installer le plugin
 openclaw plugins install @lansenger-pm/openclaw-lansenger-channel
 
-# 2. Copy to extensions directory (required due to OpenClaw CLI discovery bug)
-mkdir -p ~/.openclaw/extensions/lansenger
-cp -r ~/.openclaw/npm/node_modules/@lansenger-pm/openclaw-lansenger-channel/* \
-     ~/.openclaw/extensions/lansenger/
+# 2. Activer le plugin (si non auto-activé)
+openclaw config set plugins.entries.Lansenger.enabled true
 
-# 3. Restart gateway
+# 3. Configurer le canal (assistant interactif)
+openclaw channels add --channel Lansenger
+#   OU non-interactif :
+openclaw channels add --channel Lansenger --token "appId:appSecret"
+
+# 4. Redémarrer la passerelle
 openclaw gateway restart
 ```
 
-> ⚠️ Step 2 is required because `openclaw channels add` only discovers plugins in the `extensions/` directory, not from npm-installed packages. This is an [OpenClaw upstream bug](https://docs.openclaw.ai), not a plugin issue.
-
-### Via npm
+Les métadonnées `openclaw.install` dans `package.json` (`npmSpec`, `localPath`, `defaultChoice`) permettent l'**installation à la demande** : si un utilisateur exécute `openclaw channels add --channel Lansenger` avant que le plugin soit installé, OpenClaw peut l'installer automatiquement.
 
-```bash
-# First install the npm package manually, then configure via CLI
-npm install -g @lansenger-pm/openclaw-lansenger-channel
-openclaw channels add --channel Lansenger --app-token "your-appid" --secret "your-appsecret"
-```
+> **Passerelle personnalisée** : pour les déploiements entreprise (ex. 奇安信), configurez `apiGatewayUrl` dans `openclaw.json` ou via les variables d'environnement après la configuration — voir [Configuration optionnelle](#configuration-optionnelle).
 
 ### Installation de développement (lien local)
 
@@ -83,36 +80,18 @@ openclaw plugins install --link
 openclaw gateway restart
 ```
 
-## Configuration rapide
+### Obtenir les identifiants
 
-Après l'installation, configurez les identifiants :
+**Lansenger Desktop** → **Contacts** → **Bots** → **Personal Bots** → cliquer sur l'icône **ℹ️**
 
-> **Compte unique** : `channels add` crée un seul compte. Pour plusieurs bots, voir [Configuration multi-bot](#configuration-multi-bot) ci-dessous.
+> ⚠️ **Le client mobile ne permet PAS de voir les identifiants.** Utilisez uniquement le client desktop.
 
-```bash
-# Standard (utilise la passerelle par défaut https://open.e.lanxin.cn/open/apigw)
-openclaw channels add --channel Lansenger \
-  --app-token "your-appid" \
-  --secret "your-appsecret"
-
-# Déploiement entreprise (URL de passerelle personnalisée)
-openclaw channels add --channel Lansenger \
-  --app-token "your-appid" \
-  --secret "your-appsecret" \
-  --base-url "https://apigw.lx.qianxin.com"
-```
-
-Puis redémarrez :
-```bash
-openclaw gateway restart
-```
-
-Obtenir les identifiants : **Lansenger Desktop** → **Contacts** → **Bots** → **Personal Bots** → cliquer sur l'icône **ℹ️** (le client mobile ne permet pas de voir les identifiants).
+### Premier message
 
 Après le redémarrage, le bot se connecte automatiquement via WebSocket. Envoyez un DM au bot — vous recevrez un code de pairage. Approuvez-le :
 
 ```bash
-openclaw pairing approve lansenger <code>
+openclaw pairing approve Lansenger <code>
 ```
 
 ## Configuration
@@ -138,11 +117,11 @@ Ajoutez ces variables à `~/.openclaw/.env` ou à votre environnement :
 ```json
 {
   "channels": {
-    "lansenger": {
+    "Lansenger": {
       "appId": "your-appid",
       "appSecret": "your-secret",
       "apiGatewayUrl": "https://open.e.lanxin.cn/open/apigw",
-      "homeChannel": "lansenger",
+      "homeChannel": "Lansenger",
       "enabled": true,
       "allowFrom": ["your-appid"],
       "dmSecurity": "paired",
@@ -163,7 +142,7 @@ Ajoutez ces variables à `~/.openclaw/.env` ou à votre environnement :
 | `appId` | App ID du bot personnel | — |
 | `appSecret` | App Secret du bot personnel | — |
 | `apiGatewayUrl` | URL de la passerelle API | `https://open.e.lanxin.cn/open/apigw` |
-| `homeChannel` | Canal par défaut pour le routage de l'agent | `lansenger` |
+| `homeChannel` | Canal par défaut pour le routage de l'agent | `Lansenger` |
 | `enabled` | Activer/désactiver le canal | `true` |
 | `allowFrom` | IDs d'utilisateurs autorisés en DM | `[]` |
 | `dmSecurity` | Politique DM : `paired`, `allowlist`, `open` | `paired` |
@@ -174,15 +153,13 @@ Ajoutez ces variables à `~/.openclaw/.env` ou à votre environnement :
 
 ### Configuration multi-bot
 
-> ⚠️ `openclaw channels add` ne supporte qu'un seul compte et **remplace** le précédent à chaque exécution. Pour ajouter plusieurs bots, utilisez `openclaw config set` avec la structure `accounts`.
-
-Après avoir ajouté le premier compte via `channels add`, ajoutez des bots supplémentaires avec `openclaw config set` :
+Pour ajouter plusieurs bots, utilisez `openclaw config set` avec la structure `accounts` :
 
 ```bash
 # Ajouter un deuxième bot (remplacez appid/appsecret/gateway par vos valeurs)
-openclaw config set channels.lansenger.accounts.your-appid-2.appId "your-appid-2"
-openclaw config set channels.lansenger.accounts.your-appid-2.appSecret "your-appsecret"
-openclaw config set channels.lansenger.accounts.your-appid-2.apiGatewayUrl "https://apigw.lx.qianxin.com"
+openclaw config set channels.Lansenger.accounts.your-appid-2.appId "your-appid-2"
+openclaw config set channels.Lansenger.accounts.your-appid-2.appSecret "your-appsecret"
+openclaw config set channels.Lansenger.accounts.your-appid-2.apiGatewayUrl "https://apigw.lx.qianxin.com"
 
 # Redémarrer pour appliquer
 openclaw gateway restart
@@ -193,7 +170,7 @@ Structure de configuration résultante :
 ```json
 {
   "channels": {
-    "lansenger": {
+    "Lansenger": {
       "appId": "your-appid-2",
       "appSecret": "...",
       "dmSecurity": "paired",
@@ -254,14 +231,14 @@ Utilisez `bindings` pour router les DM Lansenger ou les conversations de groupe
     {
       agentId: "agent-a",
       match: {
-        channel: "lansenger",
+        channel: "Lansenger",
         peer: { kind: "direct", id: "2285568-xxx" },
       },
     },
     {
       agentId: "agent-a",
       match: {
-        channel: "lansenger",
+        channel: "Lansenger",
         peer: { kind: "group", id: "group-chat-id" },
       },
     },
@@ -270,7 +247,7 @@ Utilisez `bindings` pour router les DM Lansenger ou les conversations de groupe
 ```
 
 Champs de routage :
-* `match.channel`: `"lansenger"`
+* `match.channel`: `"Lansenger"`
 * `match.peer.kind`: `"direct"` (DM) ou `"group"` (chat de groupe)
 * `match.peer.id`: ID utilisateur (`2285568-xxx`) ou ID de chat de groupe
 
@@ -393,6 +370,7 @@ Les mises à jour de statut d'approbation utilisent le format DynamicMsg appCard
 
 ## Journal des modifications
 
+- **v2.8.1** — Correction README : flux d'installation en 4 étapes (installer → activer → configurer → redémarrer), suppression du hack de copie manuelle ; correction SKILL.md frontmatter (conformité AgentSkills : suppression version/category/trigger, ajout metadata.openclaw gating) ; identifiant de canal renommé en Lansenger
 - **v2.8.0** — Routage multi-agent via OpenClaw `bindings[]` (remplace `agentId` par compte) ; ajout groupPolicy/groupAllowFrom/groups pour contrôle d'accès groupe ; utilisation de `resolveAgentRoute` SDK pour routage inbound
 - **v2.7.2** — Ajout fichier VERSION ; complétion changelog dans 5 READMEs ; régénération package-lock.json
 - **v2.7.0** — Enregistrement des outils comme objets simples (pas fonctions factory) ; utilisation de l'état runtime pour client/target — correction de l'enregistrement des outils de plugin externe

package/README.md

@@ -31,7 +31,7 @@ Lansenger (蓝信) channel plugin for OpenClaw — WebSocket inbound, HTTP API o
 
 **Default strategy**: Use `formatText` first for Markdown replies. Fall back to `text` for attachments. Both `formatText` and `text` support @mention via `reminder` param — include "@姓名" in text content when mentioning.
 
-## Agent Tools (v2.5.1)
+## Agent Tools
 
 | Tool | Description |
 |------|-------------|
@@ -45,32 +45,29 @@ Lansenger (蓝信) channel plugin for OpenClaw — WebSocket inbound, HTTP API o
 | `lansenger_revoke_message` | Revoke a previously sent message |
 | `lansenger_query_groups` | Query available groups |
 
-## Quick Install
+## Installation & Configuration
 
-### Via OpenClaw CLI (recommended)
+### Recommended 4-step flow
 
 ```bash
 # 1. Install the plugin
 openclaw plugins install @lansenger-pm/openclaw-lansenger-channel
 
-# 2. Copy to extensions directory (required due to OpenClaw CLI discovery bug)
-mkdir -p ~/.openclaw/extensions/lansenger
-cp -r ~/.openclaw/npm/node_modules/@lansenger-pm/openclaw-lansenger-channel/* \
-     ~/.openclaw/extensions/lansenger/
+# 2. Enable the plugin (if not auto-enabled)
+openclaw config set plugins.entries.Lansenger.enabled true
 
-# 3. Restart gateway
+# 3. Configure the channel (interactive wizard)
+openclaw channels add --channel Lansenger
+#   OR non-interactive:
+openclaw channels add --channel Lansenger --token "appId:appSecret"
+
+# 4. Restart the gateway
 openclaw gateway restart
 ```
 
-> ⚠️ Step 2 is required because `openclaw channels add` only discovers plugins in the `extensions/` directory, not from npm-installed packages. This is an [OpenClaw upstream bug](https://docs.openclaw.ai), not a plugin issue.
-
-### Via npm
+The `openclaw.install` metadata in `package.json` (`npmSpec`, `localPath`, `defaultChoice`) enables **install-on-demand**: if a user runs `openclaw channels add --channel Lansenger` before the plugin is installed, OpenClaw can automatically install it using this metadata.
 
-```bash
-# First install the npm package manually, then configure via CLI
-npm install -g @lansenger-pm/openclaw-lansenger-channel
-openclaw channels add --channel lansenger
-```
+> **Custom gateway**: For enterprise deployments (e.g. 奇安信), set `apiGatewayUrl` in `openclaw.json` or environment after configuration — see [Optional Configuration](#optional-configuration).
 
 ### Development install (linked)
 
@@ -81,36 +78,18 @@ openclaw plugins install --link
 openclaw gateway restart
 ```
 
-## Quick Start
-
-After installing, configure credentials:
-
-> **Single account**: `channels add` creates one account. For multiple bots, see [Multi-Bot Configuration](#multi-bot-configuration) below.
+### Get Credentials
 
-```bash
-# Standard (uses default gateway https://open.e.lanxin.cn/open/apigw)
-openclaw channels add --channel Lansenger \
-  --app-token "your-appid" \
-  --secret "your-appsecret"
-
-# Enterprise deployment (custom gateway URL)
-openclaw channels add --channel Lansenger \
-  --app-token "your-appid" \
-  --secret "your-appsecret" \
-  --base-url "https://apigw.lx.qianxin.com"
-```
+**Lansenger Desktop** → **Contacts** → **Bots** → **Personal Bots** → click **ℹ️** icon
 
-Then restart:
-```bash
-openclaw gateway restart
-```
+> ⚠️ **Mobile client does NOT support viewing credentials.** Use the desktop client only.
 
-Get credentials from **Lansenger Desktop** → **Contacts** → **Bots** → **Personal Bots** → click **ℹ️** icon (mobile client cannot view credentials).
+### First message
 
-The bot will auto-connect via WebSocket on gateway restart. Send a DM to the bot — you'll receive a pairing code. Approve it:
+The bot auto-connects via WebSocket on gateway restart. Send a DM to the bot — you'll receive a pairing code. Approve it:
 
 ```bash
-openclaw pairing approve lansenger <code>
+openclaw pairing approve Lansenger <code>
 ```
 
 ## Configuration
@@ -136,11 +115,11 @@ Add these to `~/.openclaw/.env` or your environment:
 ```json
 {
   "channels": {
-    "lansenger": {
+    "Lansenger": {
       "appId": "your-appid",
       "appSecret": "your-secret",
       "apiGatewayUrl": "https://open.e.lanxin.cn/open/apigw",
-      "homeChannel": "lansenger",
+      "homeChannel": "Lansenger",
       "enabled": true,
       "allowFrom": ["your-appid"],
       "dmSecurity": "paired",
@@ -161,7 +140,7 @@ Add these to `~/.openclaw/.env` or your environment:
 | `appId` | Personal bot App ID | — |
 | `appSecret` | Personal bot App Secret | — |
 | `apiGatewayUrl` | API Gateway URL | `https://open.e.lanxin.cn/open/apigw` |
-| `homeChannel` | Default channel for agent routing | `lansenger` |
+| `homeChannel` | Default channel for agent routing | `Lansenger` |
 | `enabled` | Enable/disable the channel | `true` |
 | `allowFrom` | User IDs allowed to DM the bot | `[]` |
 | `dmSecurity` | DM policy: `paired`, `allowlist`, `open` | `paired` |
@@ -172,15 +151,13 @@ Add these to `~/.openclaw/.env` or your environment:
 
 ### Multi-Bot Configuration
 
-> ⚠️ `openclaw channels add` only supports a single account and **overwrites** the previous one each time. For multiple bots, use `openclaw config set` with the `accounts` structure below.
-
-After adding the first account via `channels add`, add additional bots using `openclaw config set`:
+For multiple bots, add additional accounts using `openclaw config set`:
 
 ```bash
 # Add a second bot (replace appid/appsecret/gateway with your values)
-openclaw config set channels.lansenger.accounts.your-appid-2.appId "your-appid-2"
-openclaw config set channels.lansenger.accounts.your-appid-2.appSecret "your-appsecret"
-openclaw config set channels.lansenger.accounts.your-appid-2.apiGatewayUrl "https://apigw.lx.qianxin.com"
+openclaw config set channels.Lansenger.accounts.your-appid-2.appId "your-appid-2"
+openclaw config set channels.Lansenger.accounts.your-appid-2.appSecret "your-appsecret"
+openclaw config set channels.Lansenger.accounts.your-appid-2.apiGatewayUrl "https://apigw.lx.qianxin.com"
 
 # Restart to apply
 openclaw gateway restart
@@ -191,7 +168,7 @@ The resulting config structure:
 ```json
 {
   "channels": {
-    "lansenger": {
+    "Lansenger": {
       "appId": "your-appid-2",
       "appSecret": "...",
       "dmSecurity": "paired",
@@ -252,14 +229,14 @@ Use `bindings` to route Lansenger DMs or groups to different agents (same patter
     {
       agentId: "agent-a",
       match: {
-        channel: "lansenger",
+        channel: "Lansenger",
         peer: { kind: "direct", id: "2285568-xxx" },
       },
     },
     {
       agentId: "agent-a",
       match: {
-        channel: "lansenger",
+        channel: "Lansenger",
         peer: { kind: "group", id: "group-chat-id" },
       },
     },
@@ -268,7 +245,7 @@ Use `bindings` to route Lansenger DMs or groups to different agents (same patter
 ```
 
 Routing fields:
-* `match.channel`: `"lansenger"`
+* `match.channel`: `"Lansenger"`
 * `match.peer.kind`: `"direct"` (DM) or `"group"` (group chat)
 * `match.peer.id`: user ID (`2285568-xxx`) or group chat ID
 
@@ -391,6 +368,7 @@ Approval status updates use the DynamicMsg appCard format. The `updateCardStatus
 
 ## Changelog
 
+- **v2.8.1** — Fix README: proper 4-step install flow (install → enable → configure → restart), remove manual-copy hack; fix SKILL.md frontmatter (AgentSkills spec compliance: remove version/category/trigger, add metadata.openclaw gating); rename channel identifier to Lansenger
 - **v2.8.0** — Use OpenClaw `bindings[]` for multi-agent routing (replaces per-account `agentId`); add groupPolicy/groupAllowFrom/groups for group chat access control; use `resolveAgentRoute` SDK for inbound routing
 - **v2.7.2** — Add VERSION file; complete changelog in all 5 READMEs; regenerate package-lock.json
 - **v2.7.0** — Register tools as plain objects (not factory functions); use runtime state for client/target — fixes external plugin tool registration

package/README.zhHans.md

@@ -33,7 +33,7 @@
 
 **默认策略**：优先使用 `formatText` 发送 Markdown 回复。附件使用 `text` 回退。两种类型均支持 @mention（通过 `reminder` 参数）—提及用户时在文本中包含"@姓名"。
 
-## 代理工具（v2.5.1）
+## 代理工具
 
 | 工具 | 说明 |
 |------|------|
@@ -47,31 +47,29 @@
 | `lansenger_revoke_message` | 撤回已发送的消息 |
 | `lansenger_query_groups` | 查询可用群组 |
 
-## 快速安装
+## 安装与配置
 
-### 通过 OpenClaw CLI（推荐）
+### 推荐 4 步流程
 
 ```bash
 # 1. 安装插件
 openclaw plugins install @lansenger-pm/openclaw-lansenger-channel
 
-# 2. 复制到 extensions 目录（因 OpenClaw CLI 发现机制 bug，必须手动复制）
-mkdir -p ~/.openclaw/extensions/lansenger
-cp -r ~/.openclaw/npm/node_modules/@lansenger-pm/openclaw-lansenger-channel/* \
-     ~/.openclaw/extensions/lansenger/
+# 2. 启用插件（如未自动启用）
+openclaw config set plugins.entries.Lansenger.enabled true
 
-# 3. 重启网关
+# 3. 配置频道（交互式向导）
+openclaw channels add --channel Lansenger
+#   或非交互式：
+openclaw channels add --channel Lansenger --token "appId:appSecret"
+
+# 4. 重启网关
 openclaw gateway restart
 ```
 
-> ⚠️ 第2步是必需的，因为 `openclaw channels add` 只发现 `extensions/` 目录下的插件，不会扫描 npm 安装的包。这是 [OpenClaw 上游 bug](https://docs.openclaw.ai)，不是插件本身的问题。
-
-### 通过 npm
+`package.json` 中的 `openclaw.install` 元数据（`npmSpec`、`localPath`、`defaultChoice`）支持**按需安装**：如果用户在插件安装前运行 `openclaw channels add --channel Lansenger`，OpenClaw 可自动安装该插件。
 
-```bash
-npm install -g @lansenger-pm/openclaw-lansenger-channel
-openclaw channels add --channel lansenger
-```
+> **自定义网关**：企业私有化部署（如奇安信）需在配置后通过 `openclaw.json` 或环境变量设置 `apiGatewayUrl` — 见[可选配置](#可选配置)。
 
 ### 开发安装（本地链接）
 
@@ -82,36 +80,18 @@ openclaw plugins install --link
 openclaw gateway restart
 ```
 
-## 快速配置
-
-安装后，配置凭证：
-
-> **单账号**：`channels add` 仅创建一个账号。如需多个机器人，见下方[多机器人配置](#多机器人配置)。
+### 获取凭证
 
-```bash
-# 标准安装（使用默认网关 https://open.e.lanxin.cn/open/apigw）
-openclaw channels add --channel Lansenger \
-  --app-token "你的-appid" \
-  --secret "你的-appsecret"
-
-# 企业私有化部署（自定义网关地址）
-openclaw channels add --channel Lansenger \
-  --app-token "你的-appid" \
-  --secret "你的-appsecret" \
-  --base-url "https://apigw.lx.qianxin.com"
-```
+**蓝信桌面端** → **通讯录** → **智能机器人** → **个人机器人** → 点击 **ℹ️** 图标
 
-然后重启：
-```bash
-openclaw gateway restart
-```
+> ⚠️ **移动端不支持查看凭证。** 请仅使用桌面端。
 
-获取凭证：**蓝信桌面端** → **通讯录** → **智能机器人** → **个人机器人** → 点击右侧 **ℹ️** 图标（移动端不支持查看凭证）。
+### 首次消息
 
 重启后机器人自动通过 WebSocket 连接。给机器人发私聊消息，会收到配对码，审批配对：
 
 ```bash
-openclaw pairing approve lansenger <配对码>
+openclaw pairing approve Lansenger <配对码>
 ```
 
 ## 配置
@@ -137,11 +117,11 @@ openclaw pairing approve lansenger <配对码>
 ```json
 {
   "channels": {
-    "lansenger": {
+    "Lansenger": {
       "appId": "your-appid",
       "appSecret": "your-secret",
       "apiGatewayUrl": "https://open.e.lanxin.cn/open/apigw",
-      "homeChannel": "lansenger",
+      "homeChannel": "Lansenger",
       "enabled": true,
       "allowFrom": ["your-appid"],
       "dmSecurity": "paired",
@@ -162,7 +142,7 @@ openclaw pairing approve lansenger <配对码>
 | `appId` | 个人机器人 App ID | — |
 | `appSecret` | 个人机器人 App Secret | — |
 | `apiGatewayUrl` | API 网关 URL | `https://open.e.lanxin.cn/open/apigw` |
-| `homeChannel` | 代理路由的默认频道 | `lansenger` |
+| `homeChannel` | 代理路由的默认频道 | `Lansenger` |
 | `enabled` | 启用/禁用频道 | `true` |
 | `allowFrom` | 允许私聊的用户 ID | `[]` |
 | `dmSecurity` | 私聊策略：`paired`、`allowlist`、`open` | `paired` |
@@ -173,15 +153,13 @@ openclaw pairing approve lansenger <配对码>
 
 ### 多机器人配置
 
-> ⚠️ `openclaw channels add` 仅支持单账号，每次执行会**覆盖**之前的账号。添加多个机器人需使用 `openclaw config set` 配置 `accounts` 结构。
-
-通过 `channels add` 添加第一个账号后，用 `openclaw config set` 添加更多机器人：
+添加多个机器人时，使用 `openclaw config set` 配置 `accounts` 结构：
 
 ```bash
 # 添加第二个机器人（替换 appid/appsecret/gateway 为你的值）
-openclaw config set channels.lansenger.accounts.your-appid-2.appId "your-appid-2"
-openclaw config set channels.lansenger.accounts.your-appid-2.appSecret "your-appsecret"
-openclaw config set channels.lansenger.accounts.your-appid-2.apiGatewayUrl "https://apigw.lx.qianxin.com"
+openclaw config set channels.Lansenger.accounts.your-appid-2.appId "your-appid-2"
+openclaw config set channels.Lansenger.accounts.your-appid-2.appSecret "your-appsecret"
+openclaw config set channels.Lansenger.accounts.your-appid-2.apiGatewayUrl "https://apigw.lx.qianxin.com"
 
 # 重启生效
 openclaw gateway restart
@@ -192,7 +170,7 @@ openclaw gateway restart
 ```json
 {
   "channels": {
-    "lansenger": {
+    "Lansenger": {
       "appId": "your-appid-2",
       "appSecret": "...",
       "dmSecurity": "paired",
@@ -253,14 +231,14 @@ openclaw gateway call lansenger.status
     {
       agentId: "agent-a",
       match: {
-        channel: "lansenger",
+        channel: "Lansenger",
         peer: { kind: "direct", id: "2285568-xxx" },
       },
     },
     {
       agentId: "agent-a",
       match: {
-        channel: "lansenger",
+        channel: "Lansenger",
         peer: { kind: "group", id: "group-chat-id" },
       },
     },
@@ -269,7 +247,7 @@ openclaw gateway call lansenger.status
 ```
 
 路由字段：
-* `match.channel`: `"lansenger"`
+* `match.channel`: `"Lansenger"`
 * `match.peer.kind`: `"direct"`（私聊）或 `"group"`（群聊）
 * `match.peer.id`: 用户 ID（`2285568-xxx`）或群聊 ID
 
@@ -392,6 +370,7 @@ Agent 路由由 OpenClaw 的 `bindings[]` 配置管理——见[多 Agent 路由
 
 ## 更新日志
 
+- **v2.8.1** — 修复 README：正确的 4 步安装流程（安装 → 启用 → 配置 → 重启），移除手动复制 hack；修复 SKILL.md frontmatter（AgentSkills 规范合规：移除 version/category/trigger，添加 metadata.openclaw gating）；channel identifier 改为 Lansenger
 - **v2.8.0** — 多 Agent 路由改用 OpenClaw `bindings[]`（替代 per-account `agentId`）；新增 groupPolicy/groupAllowFrom/groups 群聊准入控制；使用 `resolveAgentRoute` SDK 处理 inbound 路由
 - **v2.7.2** — 新增 VERSION 文件；补全 5 个 README changelog；重新生成 package-lock.json
 - **v2.7.0** — 工具注册改为纯对象（非工厂函数）；使用运行时状态获取 client/target — 修复外部插件工具注册