feishu-group-company

What This Skill Does

The feishu-group-company skill is a sophisticated configuration manager designed to orchestrate multi-bot environments within Feishu group chats. In a standard corporate setting, having multiple autonomous agents can lead to cross-talk, redundant replies, or confusion. This skill solves this by enforcing a 'Coordinator-Specialist' hierarchy.

The skill programmatically updates your openclaw.json to assign one bot as the primary coordinator (e.g., a CEO bot). It sets the group-level constraints such that the coordinator acts as the default listener, while specialist bots are 'mention-gated.' This means specialist bots will only trigger their response logic if they are explicitly @mentioned in the group. If a user tags another specialist, the coordinator bot is instructed via a dynamic system prompt to return NO_REPLY, ensuring a clean, focused user experience.

Installation

1. Ensure your OpenClaw environment is initialized and your openclaw.json is available.
2. Execute the install command: clawhub install openclaw/skills/skills/alex-shen1121/feishu-group-company.
3. Identify your group ID and the account IDs of your bots.
4. Run the provided patch script: scripts/apply_feishu_group_company.py. This script automatically migrates legacy group keys to the newer groups object structure, ensuring compatibility with OpenClaw's latest schema.
5. Restart your Gateway service to apply the new system prompts and gatekeeper configurations.

Use Cases

• Corporate Support Channels: Use a 'CEO' bot for general queries and 'UI' or 'Dev' bots for specialized, mention-triggered support.
• Bot Conflict Resolution: Prevent multiple bots from attempting to answer the same simple prompt, keeping conversation threads concise.
• Role-Based Routing: Segregate workflows by ensuring specific domains of expertise (e.g., technical documentation vs. HR policy) only respond when explicitly beckoned.

Example Prompts

1. "@UI-Bot can you check the current color palette variables for the mobile app?"
2. "@Dev-Bot, please summarize the latest deployment logs for the staging environment."
3. "What is the company policy on remote work hours?" (The coordinator bot handles this naturally without needing an @mention.)

Tips & Limitations

• Permissions: Always check that your specialist bots have 'group message' permissions enabled within the Feishu Developer Console; otherwise, they may never receive the @mention event.
• Naming: If you rename your bot account ID, you must manually update the bindings configuration, as the link between the bot's identity and its gatekeeping rule is sensitive.
• Logging: If you encounter issues, look for "rejected: no bot mention" in your logs, which confirms the gating logic is active and functioning.