feishu-chat_skill

This skill guides Feishu group messaging with explicit renderMode, @ mention handling, and card vs raw formatting to ensure consistent, reliable deliveries.

Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill feishu-chat

_meta.json630 B
SKILL.md10.5 KB

Overview

This skill is a concise Feishu (Lark) group chat messaging guide for OpenClaw. It explains raw vs card message modes, correct @ mention formats, and how to manage group members and IDs. Use it to ensure consistent formatting and reliable bot interactions in Feishu groups.

How this skill works

The skill inspects message mode configuration (renderMode) and prescribes when to use the message tool (raw/plain) versus direct session replies (card/Markdown). It documents exact @ mention syntaxes for humans, bots, and @everyone in both modes and shows how to obtain and store open_id and App ID values. It also highlights Feishu limitations like bot-to-bot messaging and required @ mentions for bots to receive messages.

When to use it

Setting or verifying Feishu renderMode in OpenClaw configuration
Sending group messages where formatting (Markdown, tables, code) must render correctly
Mentioning users or bots in Feishu groups with the correct syntax
Collecting and storing group member open_id and bot App ID values
Designing automated replies that must be visible to bots or humans

Best practices

Set channels.feishu.renderMode explicitly; prefer "card" in production for consistent formatting
Use message tool (raw) only for plain text and @ mentions; use direct reply (card) for Markdown and rich content
Never use both message tool and direct reply for the same content to avoid duplicate messages
Store group member mapping (oc_xxx -> open_id cli_xxx) in a small memory file for quick reference
Avoid unsupported Card styles: blockquote, inline code, horizontal rule, and deep nesting

Example use cases

Announcing a release with @everyone using Card mode for formatted content
Sending a plain-text alert with @human using message tool and raw @ format
Replying with code blocks, tables, or links via direct session reply in Card mode
Onboarding: ask new members to @ mention the bot so you capture their open_id
Collecting a bot App ID from a user and storing it for future @ mentions

FAQ

Card mode guarantees consistent Markdown rendering (code, tables, links) and avoids unpredictable switches caused by "auto".

How do I @ mention a bot vs a human?

In raw mode use <at user_id="ID">nickname</at>. In card mode use <at id=ID></at>. Humans use ou_xxx, bots use cli_xxx.