@wagemule/daemon 0.1.2 → 0.1.4

package/dist/skills/larksuite/lark-im/references/lark-im-messages-send.md

@@ -0,0 +1,223 @@
+# im +messages-send
+
+> **Prerequisite:** Read [`../lark-shared/SKILL.md`](../../lark-shared/SKILL.md) first to understand authentication, global parameters, and safety rules.
+
+Send a message to a group chat or a direct message conversation. Supports both user identity (`--as user`) and bot identity (`--as bot`).
+
+This skill maps to the shortcut: `lark-cli im +messages-send` (internally calls `POST /open-apis/im/v1/messages`).
+
+## Safety Constraints
+
+Messages sent by this tool are visible to other people. Before calling it, you **must** confirm with the user:
+
+1. The recipient (which person or which group)
+2. The message content
+3. The sending identity (user or bot)
+
+**Do not** send messages without explicit user approval.
+
+When using `--as bot`, the message is sent in the app's name, so make sure the app has already been added to the target chat.
+
+When using `--as user`, the message is sent as the authorized end user and requires the `im:message.send_as_user` and `im:message` scopes.
+
+## Choose The Right Content Flag
+
+| Need | Recommended flag | Why |
+|------|------|------|
+| Send plain text exactly as written | `--text` | Wrapped directly to `{"text":"..."}`; no Markdown conversion |
+| Send simple Markdown and accept Feishu-style rendering | `--markdown` | Automatically converted to `post` JSON |
+| Precisely control the final payload | `--content` | You provide the exact JSON for `text` / `post` / `interactive` / `share_*` / media payloads |
+| Send image / file / video / audio | `--image` / `--file` / `--video` / `--audio` | Shortcut uploads local files automatically |
+
+### `--text` vs `--markdown`
+
+- Use `--text` when the content should stay as plain text, including exact line breaks, indentation, code samples, shell snippets, or Markdown characters that should **not** be reinterpreted.
+- Use `--markdown` when you want basic Markdown-style rendering and you accept that the shortcut will normalize and rewrite parts of the content before sending.
+- Use `--content` when `--markdown` is not enough, especially if you need exact `post` JSON, a title, multiple locales, cards, or unsupported rich structures.
+
+## What `--markdown` Really Does
+
+`--markdown` is **not** sent as raw Markdown API content.
+
+The shortcut does all of the following before sending:
+
+1. Forces `msg_type=post`
+2. Resolves remote Markdown images like `![x](https://...)` by downloading and uploading them first
+3. Normalizes the Markdown for Feishu post rendering
+4. Wraps the result as:
+
+```json
+{"zh_cn":{"content":[[{"tag":"md","text":"..."}]]}}
+```
+
+This means `--markdown` is convenient, but it is not a full-fidelity Markdown transport.
+
+### Current Markdown Caveats
+
+- It does **not** promise full CommonMark / GitHub Flavored Markdown support.
+- It always becomes a `post` payload with a single `zh_cn` locale.
+- It does **not** let you set a `post` title. If you need a title, use `--msg-type post --content ...`.
+- Headings are rewritten:
+    - `# Title` becomes `#### Title`
+    - `##` to `######` are normalized to `#####` when the content contains H1-H3
+- Consecutive headings are separated with blank lines after heading normalization.
+- Block spacing and line breaks may be normalized during conversion.
+- Code blocks are preserved as code blocks.
+- Excess blank lines are compressed.
+- Only `http://...`, `https://...`, or already-uploaded `img_xxx` Markdown images are kept reliably.
+- Local paths in Markdown image syntax like `![x](./a.png)` are **not** auto-uploaded by `--markdown`; they may be stripped during optimization.
+- If remote Markdown image download/upload fails, that image is removed with a warning.
+
+If any of the above is unacceptable, do **not** use `--markdown`; use `--content` and provide the final JSON yourself.
+
+## Preserving Formatting
+
+If the message has multiple lines, indentation, code blocks, tabs, or many quotes/backslashes, prefer shell ANSI-C quoting with `$'...'`.
+
+This is especially useful in `zsh` / `bash` because it lets you write `\n` explicitly instead of relying on the shell to preserve literal newlines.
+
+### When formatting must be preserved
+
+Use `--text` plus `$'...'`:
+
+```bash
+lark-cli im +messages-send --chat-id oc_xxx --text $'Build failed\nBranch: feature/im-docs\nAction: please check logs'
+```
+
+```bash
+lark-cli im +messages-send --chat-id oc_xxx --text $'```bash\nmake test\nmake lint\n```'
+```
+
+Use this path when you want the receiver to see the text exactly as entered, not a converted Markdown post.
+
+### When formatting does not need exact preservation
+
+Use `--markdown`:
+
+```bash
+lark-cli im +messages-send --chat-id oc_xxx --markdown $'## Release Notes\n\n- Added send shortcut\n- Added reply shortcut'
+```
+
+This is better for lightweight readable formatting, but the final content may not match the source text byte-for-byte because the shortcut normalizes headings and spacing before sending.
+
+## Commands
+
+```bash
+# Send plain text (--text is recommended for normal messages)
+lark-cli im +messages-send --chat-id oc_xxx --text "Hello"
+
+# Equivalent manual JSON
+lark-cli im +messages-send --chat-id oc_xxx --content '{"text":"Hello"}'
+
+# Send to a direct message (pass open_id)
+lark-cli im +messages-send --user-id ou_xxx --text "Hello"
+
+# Send multi-line text while preserving formatting
+lark-cli im +messages-send --chat-id oc_xxx --text $'Line 1\nLine 2\n  indented line'
+
+# Send basic Markdown (will be converted to post JSON)
+lark-cli im +messages-send --chat-id oc_xxx --markdown $'## Update\n\n- item 1\n- item 2'
+
+# If you need exact post structure, send JSON directly
+lark-cli im +messages-send --chat-id oc_xxx --msg-type post --content '{"zh_cn":{"title":"Title","content":[[{"tag":"text","text":"Body"}]]}}'
+
+# Send a local image (uploaded automatically before sending)
+lark-cli im +messages-send --chat-id oc_xxx --image ./photo.png
+
+# Or send directly with an existing image_key
+lark-cli im +messages-send --chat-id oc_xxx --image img_xxx
+
+# Send a local file (uploaded automatically before sending)
+lark-cli im +messages-send --chat-id oc_xxx --file ./report.pdf
+
+# Send a video (--video-cover is required as the cover)
+lark-cli im +messages-send --chat-id oc_xxx --video ./demo.mp4 --video-cover ./cover.png
+lark-cli im +messages-send --chat-id oc_xxx --video ./demo.mp4 --video-cover img_xxx
+
+# Send audio
+lark-cli im +messages-send --chat-id oc_xxx --audio ./voice.opus
+
+# Use an idempotency key (same key sends only once within 1 hour)
+lark-cli im +messages-send --chat-id oc_xxx --text "Hello" --idempotency-key my-unique-id
+
+# Preview the request without executing it
+lark-cli im +messages-send --chat-id oc_xxx --markdown $'## Test\n\nhello' --dry-run
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|------|------|------|
+| `--chat-id <id>` | One of two | Group chat ID (`oc_xxx`) |
+| `--user-id <id>` | One of two | User open_id (`ou_xxx`) for direct messages |
+| `--text <string>` | One content option | Plain text message. Best default for exact text and preserved formatting. Automatically wrapped as `{"text":"..."}` |
+| `--markdown <string>` | One content option | Convenience Markdown input. Internally converted to `post` JSON with Feishu-specific normalization; not full Markdown passthrough |
+| `--content <json>` | One content option | Exact message content JSON string; use this when you need full control over `msg_type` and payload. The JSON must match the effective `--msg-type` |
+| `--image <path\|key>` | One content option | Local image path or `image_key` (`img_xxx`). Local paths are uploaded automatically |
+| `--file <path\|key>` | One content option | Local file path or `file_key` (`file_xxx`). Local paths are uploaded automatically |
+| `--video <path\|key>` | One content option | Local video path or `file_key`. Local paths are uploaded automatically. **Must be paired with `--video-cover`** |
+| `--video-cover <path\|key>` | **Required with `--video`** | Video cover image path or `image_key` (`img_xxx`). Local paths are uploaded automatically |
+| `--audio <path\|key>` | One content option | Local audio path or `file_key`. Local paths are uploaded automatically |
+| `--msg-type <type>` | No | Message type (default `text`). If you use `--text` / `--markdown` / media flags, the effective type is inferred automatically. Explicitly setting a conflicting `--msg-type` fails validation |
+| `--idempotency-key <key>` | No | Idempotency key; the same key sends only one message within 1 hour |
+| `--as <identity>` | No | Identity type: `bot` or `user` (default `bot`) |
+| `--dry-run` | No | Print the request only, do not execute it |
+
+> **Mutual exclusivity rule:** `--text`, `--markdown`, `--content`, and `--image`/`--file`/`--video`/`--audio` cannot be used together. Media flags are also mutually exclusive with each other.
+>
+> **Video cover rule:** `--video` **must** be accompanied by `--video-cover`. Omitting `--video-cover` when using `--video` will fail validation. `--video-cover` cannot be used without `--video`.
+
+## Common Mistakes
+
+- Choosing `--markdown` when you actually need exact plain text. If exact line breaks and spacing matter, use `--text`, usually with `$'...'`.
+- Assuming `--markdown` supports all Markdown features. It does not; it is converted into a Feishu `post` payload and rewritten first.
+- Putting local image paths inside Markdown like `![x](./a.png)`. `--markdown` does not auto-upload those paths.
+- Using `--content` without making the JSON match the effective `--msg-type`.
+- Explicitly setting `--msg-type` to something that conflicts with `--text`, `--markdown`, or media flags.
+- Mixing `--text`, `--markdown`, or `--content` with media flags in one command.
+
+## `content` Format Reference
+
+| `msg_type` | Example `content` |
+|----------|-------------|
+| `text` | `{"text":"Hello <at user_id=\"ou_xxx\">name</at>"}` |
+| `post` | `{"zh_cn":{"title":"Title","content":[[{"tag":"text","text":"Body"}]]}}` |
+| `image` | `{"image_key":"img_xxx"}` |
+| `file` | `{"file_key":"file_xxx"}` |
+| `audio` | `{"file_key":"file_xxx"}` |
+| `media` | `{"file_key":"file_xxx","image_key":"img_xxx"}` (video; `image_key` is the cover from `--video-cover` — **required**) |
+| `share_chat` | `{"chat_id":"oc_xxx"}` |
+| `share_user` | `{"user_id":"ou_xxx"}` |
+| `interactive` | Card JSON (see Feishu interactive card documentation) |
+
+## Return Value
+
+```json
+{
+  "message_id": "om_xxx",
+  "chat_id": "oc_xxx",
+  "create_time": "1234567890"
+}
+```
+
+## @Mention Format (text / post)
+
+- Recommended format: `<at user_id="ou_xxx">name</at>`
+- @all: `<at user_id="all"></at>`
+- The shortcut normalizes common variants like `<at id=...>` and `<at open_id=...>` into `user_id`, but you should still document examples with `user_id`
+
+## Notes
+
+- `--chat-id` and `--user-id` are mutually exclusive; you must provide exactly one
+- `--content` must be valid JSON
+- When using `--content`, you are responsible for making the JSON structure match the effective `msg_type`
+- `--image`/`--file`/`--video`/`--audio` support local file paths; the shortcut uploads first and then sends the message; both the upload and send steps use the same identity (UAT when `--as user`, TAT when `--as bot`)
+- If the provided media value starts with `img_` or `file_`, it is treated as an existing key and used directly
+- `--markdown` always sends `msg_type=post`, even if you do not explicitly set `--msg-type post`
+- If you explicitly set `--msg-type` and it conflicts with the chosen content flag, validation fails
+- When using `--video`, `--video-cover` is required as the video cover
+- `--dry-run` uses placeholder image keys for remote Markdown images and placeholder media keys for local uploads
+- Failures return an error code and message
+- `--as user` uses a user access token (UAT) and requires the `im:message.send_as_user` and `im:message` scopes; the message is sent as the authorized end user
+- `--as bot` uses a tenant access token (TAT) and requires the `im:message:send_as_bot` scope
+- When sending as a bot, the app must already be in the target group or already have a direct-message relationship with the target user

package/dist/skills/larksuite/lark-im/references/lark-im-reactions.md

@@ -0,0 +1,297 @@
+# im reactions
+
+> **Prerequisite:** Read [`../lark-shared/SKILL.md`](../../lark-shared/SKILL.md) first to understand authentication, global parameters, and safety rules.
+
+This reference is the shared annotation target for the IM reaction APIs:
+
+- `im.reactions.create`
+- `im.reactions.list`
+- `im.reactions.delete`
+- `im.reactions.batch_query`
+
+It focuses on:
+
+- What each reaction method does
+- The request/response shape you need when calling the raw API commands
+- The complete `emoji_type` list used in reaction payloads and filters
+
+> **Important:** These raw API commands accept structured input through `--params '<json>'` and `--data '<json>'`. They do not expose typed flags such as `--message-id` or `--reaction-type` directly.
+
+## Command Overview
+
+| Method | HTTP | Path | Purpose |
+|---|---|---|---|
+| `im.reactions.create` | `POST` | `/open-apis/im/v1/messages/{message_id}/reactions` | Add a reaction to one message |
+| `im.reactions.list` | `GET` | `/open-apis/im/v1/messages/{message_id}/reactions` | List reaction records on one message |
+| `im.reactions.delete` | `DELETE` | `/open-apis/im/v1/messages/{message_id}/reactions/{reaction_id}` | Delete one specific reaction record |
+| `im.reactions.batch_query` | `POST` | `/open-apis/im/v1/messages/reactions/batch_query` | Query reactions for multiple messages in one request |
+
+## Common Notes
+
+- `message_id` is always an IM message ID such as `om_xxx`
+- `reaction_id` is the unique record ID returned after a reaction is added
+- `reaction_type.emoji_type` is the enum-like emoji identifier used by both write and read APIs
+- Reaction APIs return **reaction records**, not only aggregated counts
+- When the operator is a human user, the returned ID type may depend on `user_id_type`
+
+## Inspect Schema
+
+```bash
+lark-cli schema im.reactions
+lark-cli schema im.reactions.create --format pretty
+lark-cli schema im.reactions.list --format pretty
+lark-cli schema im.reactions.delete --format pretty
+```
+
+If your local build has already exposed the batch API in `schema`, also check:
+
+```bash
+lark-cli schema im.reactions.batch_query --format pretty
+```
+
+## create
+
+Add a reaction to one message.
+
+```bash
+lark-cli im reactions create \
+  --params '{"message_id":"om_xxx"}' \
+  --data '{"reaction_type":{"emoji_type":"SMILE"}}'
+```
+
+### Request
+
+- `--params.message_id`: required message ID
+- `--data.reaction_type.emoji_type`: required emoji type
+
+### Response
+
+```json
+{
+  "reaction_id": "ZCaCIjUBVVWSrm5L-3ZTw_xxx",
+  "operator": {
+    "operator_id": "ou_xxx",
+    "operator_type": "user"
+  },
+  "action_time": "1663054162546",
+  "reaction_type": {
+    "emoji_type": "SMILE"
+  }
+}
+```
+
+## list
+
+List reaction records on one message.
+
+```bash
+lark-cli im reactions list --params '{"message_id":"om_xxx"}'
+lark-cli im reactions list --params '{"message_id":"om_xxx","reaction_type":"SMILE"}'
+lark-cli im reactions list --params '{"message_id":"om_xxx","page_size":50}'
+lark-cli im reactions list --params '{"message_id":"om_xxx","page_token":"<PAGE_TOKEN>"}'
+lark-cli im reactions list --params '{"message_id":"om_xxx","user_id_type":"open_id"}'
+```
+
+### Request Parameters (`--params`)
+
+| Parameter | Required | Description |
+|---|---|---|
+| `message_id` | Yes | Message ID (`om_xxx`) |
+| `reaction_type` | No | Filter by one emoji type such as `SMILE` or `LAUGH` |
+| `page_size` | No | Number of records per page. Default is 20 |
+| `page_token` | No | Pagination token from the previous page |
+| `user_id_type` | No | Returned operator ID type when `operator_type=user`: `open_id`, `union_id`, or `user_id` |
+
+### Response Shape
+
+```json
+{
+  "items": [
+    {
+      "reaction_id": "ZCaCIjUBVVWSrm5L-3ZTw_xxx",
+      "operator": {
+        "operator_id": "ou_xxx",
+        "operator_type": "user"
+      },
+      "action_time": "1663054162546",
+      "reaction_type": {
+        "emoji_type": "SMILE"
+      }
+    }
+  ],
+  "has_more": true,
+  "page_token": "YhljsPiGfUgnVAg9urvRFd-BvSqRLxxxx"
+}
+```
+
+### Top-Level Fields
+
+| Field | Type | Meaning |
+|---|---|---|
+| `items` | `array<object>` | Reaction records for the current page |
+| `has_more` | `boolean` | Whether more pages are available |
+| `page_token` | `string` | Token for the next page when `has_more=true` |
+
+### `items[]` Fields
+
+| Field | Type | Meaning |
+|---|---|---|
+| `reaction_id` | `string` | Unique ID of this reaction record |
+| `operator` | `object` | Identity of the user or app that added the reaction |
+| `action_time` | `string` | Unix timestamp in milliseconds |
+| `reaction_type` | `object` | Reaction payload. The key field is `emoji_type` |
+
+### `operator` Fields
+
+| Field | Type | Meaning |
+|---|---|---|
+| `operator.operator_id` | `string` | Operator ID. If `operator_type=user`, the returned ID type follows `user_id_type`; if `operator_type=app`, this is the app ID |
+| `operator.operator_type` | `string` | `user` or `app` |
+
+## delete
+
+Delete one specific reaction record from one message.
+
+```bash
+lark-cli im reactions delete \
+  --params '{"message_id":"om_xxx","reaction_id":"ZCaCIjUBVVWSrm5L-3ZTw_xxx"}'
+```
+
+### Request
+
+- `--params.message_id`: required message ID
+- `--params.reaction_id`: required reaction record ID
+
+### Response
+
+The response shape is similar to `create`, and usually echoes:
+
+- `reaction_id`
+- `operator`
+- `action_time`
+- `reaction_type.emoji_type`
+
+## batch_query
+
+Query reactions for multiple messages in one request.
+
+```bash
+lark-cli im reactions batch_query \
+  --params '{"user_id_type":"open_id"}' \
+  --data '{
+    "queries":[
+      {"message_id":"om_xxx"},
+      {"message_id":"om_yyy","page_token":"<PAGE_TOKEN>"}
+    ],
+    "page_size_per_message":10,
+    "reaction_type":"LAUGH"
+  }'
+```
+
+### Request
+
+#### `--params`
+
+| Parameter | Required | Description |
+|---|---|---|
+| `user_id_type` | No | Returned user ID type in operator info: `open_id`, `union_id`, or `user_id` |
+
+#### `--data`
+
+| Field | Required | Description |
+|---|---|---|
+| `queries` | Yes | Array of target messages |
+| `queries[].message_id` | No | Message ID to query |
+| `queries[].page_token` | No | Continuation token for that message |
+| `page_size_per_message` | No | Max reactions returned per message |
+| `reaction_type` | No | Filter by one emoji type |
+
+### Response
+
+The meta definition contains three top-level result groups:
+
+| Field | Meaning |
+|---|---|
+| `success_msg_reaction_details` | Per-message reaction detail records |
+| `success_msg_reaction_counts` | Per-message aggregated reaction counts |
+| `fail_msg_reaction_details` | Query failures for individual messages |
+
+#### `success_msg_reaction_details`
+
+Each `message_reaction_items[]` element includes:
+
+- `reaction_id`
+- `operator`
+- `action_time`
+- `emoji_type`
+
+#### `success_msg_reaction_counts`
+
+Each aggregated count record includes:
+
+- `message_id`
+- `reaction_count[].reaction_type`
+- `reaction_count[].count`
+
+#### `fail_msg_reaction_details`
+
+Each failed message record includes:
+
+- `message_id`
+- `fail_reason`
+
+Supported `fail_reason` values from meta:
+
+- `invalid`
+- `invalid_page_token`
+- `no_permission`
+
+## `emoji_type` Field
+
+Reaction emoji identifiers are used in slightly different field names across the APIs:
+
+- `im.reactions.create`: request and response use `reaction_type.emoji_type`
+- `im.reactions.list`: request filter uses `reaction_type`, response uses `reaction_type.emoji_type`
+- `im.reactions.delete`: response uses `reaction_type.emoji_type`
+- `im.reactions.batch_query`: request filter uses top-level `reaction_type`, detail results use `message_reaction_items[].emoji_type`, aggregated results use `reaction_count[].reaction_type`
+
+## Complete `emoji_type` List
+
+The following list is synchronized from the official Feishu reaction emoji documentation:
+
+- Source page: `https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/im-v1/message-reaction/emojis-introduce`
+- Markdown source: `https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/im-v1/message-reaction/emojis-introduce.md`
+
+Current count in the fetched source: `185`.
+
+```text
+OK, THUMBSUP, THANKS, MUSCLE, FINGERHEART, APPLAUSE, FISTBUMP, JIAYI
+DONE, SMILE, BLUSH, LAUGH, SMIRK, LOL, FACEPALM, LOVE
+WINK, PROUD, WITTY, SMART, SCOWL, THINKING, SOB, CRY
+ERROR, NOSEPICK, HAUGHTY, SLAP, SPITBLOOD, TOASTED, GLANCE, DULL
+INNOCENTSMILE, JOYFUL, WOW, TRICK, YEAH, ENOUGH, TEARS, EMBARRASSED
+KISS, SMOOCH, DROOL, OBSESSED, MONEY, TEASE, SHOWOFF, COMFORT
+CLAP, PRAISE, STRIVE, XBLUSH, SILENT, WAVE, WHAT, FROWN
+SHY, DIZZY, LOOKDOWN, CHUCKLE, WAIL, CRAZY, WHIMPER, HUG
+BLUBBER, WRONGED, HUSKY, SHHH, SMUG, ANGRY, HAMMER, SHOCKED
+TERROR, PETRIFIED, SKULL, SWEAT, SPEECHLESS, SLEEP, DROWSY, YAWN
+SICK, PUKE, BETRAYED, HEADSET, EatingFood, MeMeMe, Sigh, Typing
+Lemon, Get, LGTM, OnIt, OneSecond, VRHeadset, YouAreTheBest, SALUTE
+SHAKE, HIGHFIVE, UPPERLEFT, ThumbsDown, SLIGHT, TONGUE, EYESCLOSED, RoarForYou
+CALF, BEAR, BULL, RAINBOWPUKE, ROSE, HEART, PARTY, LIPS
+BEER, CAKE, GIFT, CUCUMBER, Drumstick, Pepper, CANDIEDHAWS, BubbleTea
+Coffee, Yes, No, OKR, CheckMark, CrossMark, MinusOne, Hundred
+AWESOMEN, Pin, Alarm, Loudspeaker, Trophy, Fire, BOMB, Music
+XmasTree, Snowman, XmasHat, FIREWORKS, 2022, REDPACKET, FORTUNE, LUCK
+FIRECRACKER, StickyRiceBalls, HEARTBROKEN, POOP, StatusFlashOfInspiration, 18X, CLEAVER, Soccer
+Basketball, GeneralDoNotDisturb, Status_PrivateMessage, GeneralInMeetingBusy, StatusReading, StatusInFlight, GeneralBusinessTrip, GeneralWorkFromHome
+StatusEnjoyLife, GeneralTravellingCar, StatusBus, GeneralSun, GeneralMoonRest, MoonRabbit, Mooncake, JubilantRabbit
+TV, Movie, Pumpkin, BeamingFace, Delighted, ColdSweat, FullMoonFace, Partying
+GoGoGo, ThanksFace, SaluteFace, Shrug, ClownFace, HappyDragon
+```
+
+## References
+
+- [lark-im](../SKILL.md) - all IM commands
+- [lark-shared](../../lark-shared/SKILL.md) - authentication and global parameters
+- Official emoji doc: `https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/im-v1/message-reaction/emojis-introduce`

package/dist/skills/larksuite/lark-im/references/lark-im-threads-messages-list.md

@@ -0,0 +1,111 @@
+# im +threads-messages-list
+
+> **Prerequisite:** Read [`../lark-shared/SKILL.md`](../../lark-shared/SKILL.md) first to understand authentication, global parameters, and safety rules.
+
+Fetch the reply message list inside a thread. When `im +chat-messages-list` returns messages that include a `thread_id` field, use this command to inspect all replies in that thread.
+
+This skill maps to the shortcut: `lark-cli im +threads-messages-list` (internally calls `GET /open-apis/im/v1/messages` with `container_id_type=thread` to fetch thread messages).
+
+## Commands
+
+```bash
+# Get thread replies (ascending by time by default, table output)
+lark-cli im +threads-messages-list --thread omt_xxx
+
+# Reverse chronological order (latest first)
+lark-cli im +threads-messages-list --thread omt_xxx --sort desc
+
+# Control page size
+lark-cli im +threads-messages-list --thread omt_xxx --page-size 20
+
+# Pagination
+lark-cli im +threads-messages-list --thread omt_xxx --page-token <PAGE_TOKEN>
+
+# Output format options
+lark-cli im +threads-messages-list --thread omt_xxx --format pretty
+lark-cli im +threads-messages-list --thread omt_xxx --format table
+lark-cli im +threads-messages-list --thread omt_xxx --format csv
+
+# View as a bot
+lark-cli im +threads-messages-list --thread omt_xxx --as bot
+
+# Preview the request without executing it
+lark-cli im +threads-messages-list --thread omt_xxx --dry-run
+```
+
+## Parameters
+
+| Parameter | Required | Description |
+|------|------|------|
+| `--thread <id>` | Yes | Thread ID (`om_xxx` or `omt_xxx` format) |
+| `--sort <order>` | No | Sort order: `asc` (default) / `desc` |
+| `--page-size <n>` | No | Number of items per page (default 50, range 1-500) |
+| `--page-token <token>` | No | Pagination token for the next page |
+| `--format <fmt>` | No | Output format: `json` (default) / `pretty` / `table` / `ndjson` / `csv` |
+| `--as <identity>` | No | Identity type: `user` (default) / `bot` |
+| `--dry-run` | No | Print the request only, do not execute it |
+
+## Core Constraints
+
+### 1. Source of `thread_id`
+
+`thread_id` (`omt_xxx` or `om_xxx`) comes from the `thread_id` field in results returned by `im +chat-messages-list` or `im +messages-search`. Do not guess a thread ID. Fetch messages first and use the returned value.
+
+### 2. No time filtering support
+
+Thread messages do not support `start_time` / `end_time` filtering because of Feishu API limitations. Use pagination and sort order to control the scope.
+
+### 3. Pagination (`has_more` / `page_token`)
+
+- When the result includes `has_more=true`, use `page_token` to fetch the next page
+- If you need the complete thread, keep paginating; if you only need an overview, the first page is often enough
+
+### 4. Recommended expansion strategy
+
+| Scenario | Recommended Parameters |
+|------|---------|
+| Quickly inspect recent replies | `--sort desc --page-size 10` |
+| Read the full thread in chronological order | `--sort asc --page-size 50`, then paginate as needed |
+| Just confirm whether replies exist | `--sort desc --page-size 1` |
+
+## Usage Scenarios
+
+### Scenario 1: Expand a thread discovered in group messages
+
+```bash
+# Step 1: Fetch group messages and find one that contains thread_id
+lark-cli im +chat-messages-list --chat-id oc_xxx
+
+# Step 2: Extract thread_id from the JSON output and fetch thread replies
+lark-cli im +threads-messages-list --thread omt_xxx
+```
+
+### Scenario 2: Paginate through a long thread
+
+```bash
+# First page
+lark-cli im +threads-messages-list --thread omt_xxx
+
+# If has_more=true is returned, continue with page_token
+lark-cli im +threads-messages-list --thread omt_xxx --page-token <PAGE_TOKEN>
+```
+
+## Resource Rendering
+
+Thread replies are rendered into human-readable text. Image messages appear as placeholders such as `[Image: img_xxx]`; resource binaries are **not** downloaded automatically.
+
+Other resource types (files, audio, video) still need to be downloaded manually through `im +messages-resources-download`. See [lark-im-messages-resources-download](lark-im-messages-resources-download.md).
+
+## Common Errors and Troubleshooting
+
+| Symptom | Root Cause | Solution |
+|---------|---------|---------|
+| "Invalid thread ID format" | `thread_id` does not start with `om_` or `omt_` | Use a valid `om_xxx` or `omt_xxx` value |
+| Empty thread result | Wrong thread_id or no replies in the thread | Confirm the thread_id came from `im +chat-messages-list` output |
+| Permission denied | The user is not authorized or is not a conversation member | Make sure OAuth authorization is complete and the identity is a chat member |
+
+## References
+
+- [lark-im](../SKILL.md) - all message-related commands
+- [lark-im-chat-messages-list](lark-im-chat-messages-list.md) - fetch conversation messages (source of `thread_id`)
+- [lark-shared](../../lark-shared/SKILL.md) - authentication and global parameters