feishu-cli-messaging

Original：🇨🇳 Chinese

Translated

6 scripts

Unified entry for Feishu instant messaging, covering sending, replying, forwarding, merged forwarding, urgent messaging and resource downloading, reading chat history, Reaction, Pin and group member management, constructing V2 interactive cards, and WebSocket event subscription. This Skill must be used when users request to send messages or notifications, view or export group chats, manage group members, create Feishu cards for alerts/approvals/reports/dashboards/marketing promotions/festival greetings/brand displays/hand-drawn or dark-themed creatives/cards with buttons or charts, listen to real-time message or approval events, or process message attachments. This Skill must be triggered as long as the target carrier is Feishu chat or group messages, or the request contains terms like msg/chat/card/event, post/interactive, oc_/om_, Reaction, Pin, urgent messaging or local images in messages, even if the user doesn't explicitly mention CLI. Do not use it for email reading/replying/drafting, nor for meeting recording, Minutes or verbatim transcripts; use feishu-cli-mail and feishu-cli-meetings for those respectively. Use feishu-cli-platform for global message search.

2installs

Sourceriba2534/feishu-cli

Added on2026-08-22

NPX Install

npx skill4agent add riba2534/feishu-cli feishu-cli-messaging

SKILL.md Content (Chinese)

View Translation Comparison →

Feishu Instant Messaging

After loading the workflow, resolve the relative paths of

references/

,

scripts/

,

templates/

, and

examples/

based on the directory where this

workflow.md

is located; use the resolved actual path when executing scripts, and do not rely on the current shell directory.

Routing

Intent	File to Read
Send, reply, forward, urgent messaging, flag, resource download	`references/workflows/msg/workflow.md`
Historical messages, details, Reaction, Pin, recall, groups and members	`references/workflows/chat/workflow.md`
Design and generate V2 interactive card JSON	`references/workflows/card/workflow.md`
Subscribe to and consume real-time events	`references/workflows/event/workflow.md`

When sending interactive cards, first read the card construction JSON, then read the msg to send. When searching keywords in historical messages, read

../feishu-cli-platform/references/workflows/search/workflow.md

.

Execution Rules

Confirm the recipient type and ID before sending; do not mix up email, open_id, and chat_id.
Group messaging, urgent messaging, and message deletion have external impacts; display the targets and quantities first.
```
msg send
```
and
```
msg reply
```
share content shortcut parameters; local images, files, Opus audio, and MP4 videos will be uploaded first. Any missing file, illegal format, or upload failure will prevent message submission.
```
--upload-images
```
applies to both commands.
To enter an existing thread, must use
```
msg reply <om_xxx>
```
;
```
omt_xxx
```
is only used for thread query/forwarding and cannot be used as the recipient of
```
msg send
```
. Add
```
--reply-in-thread
```
only when starting a new thread in a regular message group.
Use the same
```
--idempotency-key
```
for retries of sending and replying; media uploads may be redone, but the server-side idempotency key prevents duplicate visible messages. Success is only determined when the command returns a non-empty
```
message_id
```
.

For troubleshooting external group 232033, read

references/workflows/chat/references/external-chat.md

.

Validate card drafts and sending candidates separately; before sending, must run
```
lint_card.py --strict
```
from the card workflow, and do not send cards containing placeholders, sample IDs, fake links, or unconnected callback buttons.
Use the 19 built-in presets in the card workflow when the user specifies a card style; when using local header images or icon materials, pass
```
--upload-images
```
for both lint and actual
```
msg send
```
/
```
msg reply
```
, and do not hardcode cross-tenant
```
img_key
```
.