@lansenger-pm/openclaw-lansenger-channel 2.3.2 → 2.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/lansenger-messaging/SKILL.md +4 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lansenger-pm/openclaw-lansenger-channel",
3
- "version": "2.3.2",
3
+ "version": "2.3.4",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "files": [
package/skills/lansenger-messaging/SKILL.md CHANGED
@@ -10,6 +10,8 @@ trigger: When the current session channel is lansenger, or when you need to send
10
10
 
11
11
  You are communicating on Lansenger, an enterprise messaging platform. Understanding its message type rules is critical — choosing the wrong type causes silent feature loss (Markdown ignored, attachments dropped, @mentions invisible).
12
12
 
13
+ **This SKILL is reference documentation, NOT a CLI command.** Do NOT generate commands like `openclaw skill lansenger-messaging --message ...` — that command does not exist and will fail. To send messages, use the agent tools (`lansenger_send_file`, `lansenger_send_text`, etc.) directly.
14
+
13
15
  ## Auto-Routing: msgTarget(chatId)
14
16
 
15
17
  All outbound methods use the `msgTarget` helper internally — **no separate group/private methods exist**. Just pass the chatId and routing happens automatically:
@@ -199,7 +201,8 @@ openclaw pairing approve lansenger <code>
199
201
  - **AppArticles uses `description` not `summary`** — the article description field is called `description`, not `summary`
200
202
  - **`text-indent` MUST have units** — bare `0` causes empty API response; use `0em`
201
203
  - **Dynamic cards require `headStatusInfo`** — auto-filled if omitted, but explicit is better
202
- - **Personal bots only** — organization/enterprise bots are NOT supported
204
+ - **Gateway URL is per-environment** — the plugin uses whatever `apiGatewayUrl` is configured (e.g. `https://apigw.lx.qianxin.com` for 奇安信 environments, or `https://open.e.lanxin.cn/open/apigw` for standard Lansenger). All API endpoints are appended to this base URL. Do NOT assume the default gateway — always use the configured value.
205
+ - **`openclaw skill` and `openclaw message lansenger` do NOT exist** — this SKILL is documentation only, not a CLI command. Third-party plugin channels are not in `openclaw message send --channel`. To send messages, use agent tools directly.
203
206
  - **Message length limit** ~4000 characters
204
207
  - **File size limits** depend on organization's Lansenger configuration
205
208
  - **Credentials** in Lansenger Desktop → Contacts → Bots → Personal Bot → ℹ️ icon