Feishu Group Company
Overview
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 INLINECODE0
Quick start
- 1. 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
What this skill changes
For the target group:
- - Top-level group rule becomes INLINECODE5
- Specialist bot accounts get per-account override INLINECODE6
- Coordinator bot account gets per-account override INLINECODE7
- 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 INLINECODE11
Important notes
- - 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.
When behavior is still wrong
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
Resources
scripts/
- -
apply_feishu_group_company.py — patch openclaw.json for one company group pattern
references/
- -
troubleshooting.md — quick diagnosis checklist and expected log signatures
飞书企业群组
概述
使用此技能可标准化一个共享的飞书企业群组，其中包含一个默认协调机器人及多个专业机器人。
目标行为：
- - 群内无@提及 → 仅协调机器人回复
- @提及专业机器人 → 仅该专业机器人回复
- 当明确提及另一个机器人时，协调机器人返回NO_REPLY
快速开始
- 1. 确认群聊ID（ocxxx）及所有机器人的飞书账号ID。
- 确定默认协调机器人，通常为company-ceo。
- 针对~/.openclaw/openclaw.json运行scripts/applyfeishugroupcompany.py。
- 如有需要，重新加载/重启Gateway。
- 通过两项测试进行验证：
- 无@提及的普通消息
- 提及专业机器人的消息
此技能的变更内容
针对目标群组：
- - 顶级群组规则变为requireMention: true
- 专业机器人账号获得按账号覆盖groups..requireMention: true
- 协调机器人账号获得按账号覆盖groups..requireMention: false
- 协调机器人获得群组范围的systemPrompt，强制执行：
- 无@提及 → 正常回复
- @其他用户/机器人但非协调机器人 → NO_REPLY
- @协调机器人 → 正常回复
- - 移除旧的无效按账号键group，改用groups
重要说明
- - 在channels.feishu.accounts.下使用groups而非group。
- 若重命名飞书账号ID，请同时更新引用该ID的bindings[].match.accountId。
- 若专业机器人拥有群消息权限，仍可能在传输层接收事件；关键在于它们受提及限制，因此会拒绝非提及消息。
- 当明确提及另一个机器人时，协调机器人必须保持静默；此技能通过群组systemPrompt实现。
- 若专业机器人在被@提及后仍未收到群流量，请先检查飞书应用权限。
行为异常时的处理
阅读references/troubleshooting.md并检查日志中的以下模式：
- rejected: no bot mention
- dispatch complete (replies=0)
- 该账号完全没有入站日志行
资源
scripts/
- - applyfeishugroup_company.py — 为单一企业群组模式修补openclaw.json
references/
- - troubleshooting.md — 快速诊断检查清单及预期日志特征
