Feishu Group Company

核心功能是标准化飞书企业群机器人响应逻辑：无@时仅默认协调机器人回复，@专属机器人时仅对应机器人回复，协调机器人在@其他机器人时静默。适用于企业/工作组群，如CEO机器人默认回复、@UI/Dev时对应机器人响应。输入为群ID、机器人账号ID，通过脚本修改配置文件生效，配套故障排查指引。

热度 42.25

最近更新 2026-05-11 17:38:22

分类：自动化依赖：代码执行 / 读写文件应用场景：自动化脚本 / 工作流 / 任务管理

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add feishu-group-company

Metadata

name: feishu-group-company
description: Configure a Feishu multi-bot company group so one coordinator bot, for example `company-ceo`, handles normal group messages, while specialist bots reply only when explicitly @mentioned. Use when setting up or fixing a shared company/work group with multiple Feishu bot accounts, especially for patterns like: normal messages then CEO replies; at UI then UI replies; at dev then dev replies; and CEO stays silent when another bot is explicitly mentioned.

Use this skill to standardize a shared Feishu company group with one default coordinator bot and multiple specialist bots.

Target behavior:

No @mention in the group → only the coordinator bot replies
@mention a specialist bot → only that specialist replies
When another bot is explicitly mentioned, the coordinator bot returns NO_REPLY

Confirm the group chat ID (oc_xxx) and the Feishu account IDs for all bots.
Decide which bot is the default coordinator, usually company-ceo.
Run scripts/apply_feishu_group_company.py against ~/.openclaw/openclaw.json.
Reload/restart Gateway if needed.
Verify with two tests:
- plain message with no @mention
- message that @mentions a specialist bot

For the target group:

Top-level group rule becomes requireMention: true
Specialist bot accounts get per-account override groups.<chatId>.requireMention: true
Coordinator bot account gets per-account override groups.<chatId>.requireMention: false
Coordinator bot gets a group-scoped systemPrompt that enforces:
- no @mention → reply normally
- @other user/bot but not coordinator → NO_REPLY
- @coordinator → reply normally
Legacy invalid per-account key group is removed in favor of groups

Use groups, not group, under channels.feishu.accounts.<accountId>.
If you rename a Feishu account ID, also update any bindings[].match.accountId that reference it.
Specialist bots may still receive the event at transport level if they have group-message permissions; the important part is that they are mention-gated and therefore reject non-mentioned messages.
The coordinator bot must still be instructed to stay silent when another bot is explicitly mentioned; this skill does that via group systemPrompt.
If a specialist bot never receives group traffic even when @mentioned, check Feishu app permissions first.

Read references/troubleshooting.md and check logs for these patterns:

Good specialist rejection on plain message:
- rejected: no bot mention
Good coordinator silence when another bot is mentioned:
- dispatch complete (replies=0)
Broken specialist delivery:
- no inbound log lines for that account at all

apply_feishu_group_company.py — patch openclaw.json for one company group pattern