@lansenger-pm/openclaw-lansenger-channel 2.4.2 → 2.4.3

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 +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lansenger-pm/openclaw-lansenger-channel",
3
- "version": "2.4.2",
3
+ "version": "2.4.3",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "files": [
package/skills/lansenger-messaging/SKILL.md CHANGED
@@ -42,7 +42,7 @@ Lansenger has two outbound text types that cannot be combined:
42
42
  ### What this means for you
43
43
 
44
44
  - **Normal replies** → just write Markdown. It's automatically sent as formatText.
45
- - **Need @mention** → formatText supports `reminder` (newer API), but you MUST include "@姓名" in the message text so the user sees who was mentioned. Example: write `"@张三 重要通知：明天开会"` and set `reminderUserIds: ["staffId-of-张三"]`. Old API environments silently accept reminder but won't show the notification on client — the explicit "@姓名" in text ensures clarity regardless.
45
+ - **@mention is optional, but recommended in group chat** → In group chat, @mention the person you're replying to so they know the message is directed at them. When using reminder, include "@姓名" in the text. Example: `"@张三 明天开会"` with `reminderUserIds: ["staffId-of-张三"]`. Old API silently accepts reminder but won't show notification — the "@姓名" in text ensures clarity regardless.
46
46
  - **Need to attach a file/image/video** → Markdown won't work. Use `lansenger_send_file`. If you need both formatting AND a file, send the Markdown reply first, then call `lansenger_send_file` separately.
47
47
  - **Never put raw Markdown in a plain-text message** — it displays as ugly source code to the user.
48
48
 
@@ -98,7 +98,7 @@ lansenger_send_text(content=<plain text>, filePath=<optional local path>, to=<op
98
98
 
99
99
  - **NO Markdown** — content is plain text only
100
100
  - `filePath` optional — if provided, content becomes caption for the attachment
101
- - `reminderAll` / `reminderUserIds` — @mention members. **You MUST include "@姓名" in the message text** so the user can see who was mentioned. For text type: client shows @notification. For formatText: newer API supports reminder, old API silently accepts it but client won't show notification — the explicit "@姓名" text ensures clarity regardless. (group/staff chat only, NOT DMs)
101
+ - `reminderAll` / `reminderUserIds` — optional @mention. In group chat, recommended to @mention the person you're replying to. When using reminder, include "@姓名" in the text so users can see who was mentioned. (group/staff chat only, NOT DMs)
102
102
 
103
103
  ## Sending Images from URLs
104
104
 
@@ -196,7 +196,7 @@ openclaw pairing approve lansenger <code>
196
196
 
197
197
  - **Markdown is default** — write normally, it renders automatically
198
198
  - **Never put Markdown in a plain-text message** — displays as raw source code
199
- - **Never put @mentions in a Markdown message without "@姓名" text** — reminder works in formatText (newer API), but you must write "@姓名" explicitly so users can see who was mentioned
199
+ - **@mention in group chat is recommended** — when replying to someone in a group, @mention them so they know the message is for them; include "@姓名" in the text
200
200
  - **MEDIA: tags work for workspace files** — for non-workspace paths (Documents, /tmp, etc.), use `lansenger_send_file` instead
201
201
  - **AppArticles uses `description` not `summary`** — the article description field is called `description`, not `summary`
202
202
  - **`text-indent` MUST have units** — bare `0` causes empty API response; use `0em`