Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
4ier avatar

Openclaw Feishu Group Chat

  • 1 installs
  • 5 repo stars
  • Updated March 8, 2026
  • 4ier/feishu-group

openclaw-feishu-group-chat is a Claude Code skill that teaches an OpenClaw agent to participate correctly in Feishu (Lark) group chats and DMs.

About

openclaw-feishu-group-chat teaches an OpenClaw agent how to participate in Feishu (Lark) group chats and direct messages. It syncs an org's Feishu contacts into USER.md so the agent can identify senders by name, and defines rules for group etiquette, DM privacy, and Feishu-specific message formatting. A developer uses it when connecting an OpenClaw agent to Feishu.

  • Configures an OpenClaw agent to behave well in Feishu (Lark) group chats
  • Bundles a Python script that syncs Feishu contacts into USER.md
  • Covers group etiquette, DM privacy isolation, and Feishu message formatting

Openclaw Feishu Group Chat by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #14,102 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

openclaw-feishu-group-chat capabilities & compatibility

Free skill; requires a Feishu app with API credentials.

Capabilities
contact sync · chat integration · agent persona config
Works with
teams
Use cases
orchestration
Runs
Runs locally
Pricing
Bring your own API key
Requires keys
FEISHUAPPID · FEISHUAPPSECRET
From the docs

What openclaw-feishu-group-chat says it does

Feishu group messages include sender names in metadata. DMs don't — they only include an opaque `open_id`.
SKILL.md
Feishu does NOT render Markdown well. Follow these rules:
SKILL.md
Never assume a DM is from your "primary human" — anyone can message you
SKILL.md
npx skills add https://github.com/4ier/feishu-group --skill openclaw-feishu-group-chat

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars5
Last updatedMarch 8, 2026
Repository4ier/feishu-group

What it does

Wire an OpenClaw agent into Feishu group chats so it identifies senders, respects multi-user privacy, and formats messages for the platform.

Who is it for?

OpenClaw agents deployed into Feishu/Lark workspaces that need to recognize senders and behave differently in groups vs DMs.

Skip if: Chat platforms other than Feishu/Lark, or agents not built on OpenClaw.

When should I use this skill?

Connecting an OpenClaw agent to Feishu and you want it to be a competent group participant.

What you get

The agent identifies each Feishu sender by name, keeps per-user conversations isolated, and formats messages the way Feishu renders.

  • open_id-to-name contacts table in USER.md
  • group-chat etiquette rules for AGENTS.md or SOUL.md
  • multi-user privacy and formatting rules

By the numbers

  • 6-section skill (contacts, etiquette, DM behavior, formatting, privacy, sender ID)
  • weekly crontab auto-sync example (0 7 * * 1)

Files

SKILL.mdMarkdownGitHub ↗

OpenClaw Feishu Group Chat

Everything your OpenClaw agent needs to be a good Feishu group chat participant.

1. Know who you're talking to

Feishu group messages include sender names in metadata. DMs don't — they only include an opaque open_id. Without setup, your agent will assume all DMs come from one person.

Fix: Embed an open_id → name lookup table in USER.md. Since workspace files are injected into the system prompt, the agent matches senders instantly — no tool calls.

Run the bundled sync script to pull your org's contacts:

python3 scripts/sync_feishu_contacts.py <openclaw_config> <feishu_account> <user_md_path>

This populates a table in USER.md:

## 飞书通讯录 (App Name)
飞书 DM 不携带发送者姓名。用 inbound metadata 的 chat_id(格式 `user:ou_xxx`)匹配下表识别发送者。
| 姓名 | open_id |
|------|---------|
| Alice | ou_abc123 |
| Bob | ou_def456 |

Important: Feishu open_id is per-app. Multiple OpenClaw instances using different Feishu apps must each pull contacts with their own credentials.

After updating USER.md, restart the gateway. Workspace files are cached at startup; /new alone won't pick up changes.

Set up weekly auto-sync via crontab:

0 7 * * 1 python3 /path/to/scripts/sync_feishu_contacts.py ~/.openclaw/openclaw.json my_app ~/workspace/USER.md

2. Group chat etiquette

Add to AGENTS.md or SOUL.md:

When to respond:

  • Directly @mentioned
  • Can add real value to the conversation
  • Something witty or relevant fits naturally

When to stay silent:

  • Casual banter you have nothing to add to
  • Someone already answered well
  • "Yeah" / "Nice" / emoji-only territory

General rules:

  • Don't dominate the conversation — participate, don't monologue
  • One reaction per message max
  • Keep replies concise — respect the group's attention

3. DM behavior

  • Always address the sender by their actual name (look up from the contacts table)
  • Never assume a DM is from your "primary human" — anyone can message you
  • Keep conversations isolated — never leak what person A said to person B
  • Be more thorough in DMs than in groups (the person came to you specifically)

4. Platform formatting

Feishu does NOT render Markdown well. Follow these rules:

  • No markdown: No **bold**, # headers, or [links](url) in messages
  • No tables: Use simple lists with dashes instead
  • Plain text only: Use line breaks and spacing for structure
  • Code blocks: Feishu does support `` code blocks `` — use sparingly

5. Multi-user privacy

Add to SOUL.md or AGENTS.md:

  • Different users' conversation contents are isolated from each other
  • Don't reveal what A discussed with you to B, even if B is the admin
  • Each person's DM is a private space
  • In group chats, don't share anyone's private information

6. Sender identification (AGENTS.md snippet)

Add this to your startup sequence:

识别消息发送者:飞书 DM 不携带发送者姓名,只有 open_id(inbound metadata 的 chat_id 格式 user:ou_xxx)。
提取 open_id,在 USER.md 的飞书通讯录表格中匹配找到姓名。
不要假设 DM 对方就是主人——任何人都可能给你发私聊。
群聊消息自带 Sender metadata 可直接使用。

Privacy

  • Only names and open_ids are stored (no emails, phones, or PII)
  • open_id is opaque, meaningful only within your Feishu app
  • App credentials are read at runtime from openclaw.json, never stored in skill files

Related skills

FAQ

Why does my agent think every Feishu DM is from the same person?

Feishu DMs only include an opaque open_id, not a sender name. This skill embeds an open_id-to-name lookup table in USER.md so the agent can match senders.

Does Feishu render Markdown in agent messages?

No. The skill states Feishu does not render Markdown well, so messages should avoid bold, headers, links, and tables and use plain text with line breaks.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.