ClawHub

Feishu Group Company

v1.0.0

Configure a Feishu multi-bot company group so one coordinator bot, for example `company-ceo`, handles normal group messages, while specialist bots reply only...

⭐ 0· 117·0 current·0 all-time
byAlexShen@alex-shen1121

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for alex-shen1121/feishu-group-company.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Feishu Group Company" (alex-shen1121/feishu-group-company) from ClawHub.
Skill page: https://clawhub.ai/alex-shen1121/feishu-group-company
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install feishu-group-company

ClawHub CLI

Package manager switcher

npx clawhub@latest install feishu-group-company
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (configure a Feishu multi-bot company group) matches the included script and SKILL.md. The script patches ~/.openclaw/openclaw.json to set group-level requireMention, per-account groups entries, and a coordinator systemPrompt—exactly what the skill claims to do.
✓
Instruction Scope
SKILL.md instructs the operator to run the provided script against the OpenClaw config and to verify behavior. The instructions reference only the OpenClaw config, group IDs, and account IDs (all directly relevant). There are no instructions to read unrelated files, environment variables, or to transmit data externally.
✓
Install Mechanism
No install spec; this is an instruction-only skill with a small Python script. No downloads, package installs, or archives are performed. Risk from install mechanism is minimal.
✓
Credentials
The skill requests no environment variables, no credentials, and no config paths beyond the OpenClaw config (default ~/.openclaw/openclaw.json) described in the docs. That access is proportionate to the stated purpose of editing OpenClaw Feishu routing.
ℹ
Persistence & Privilege
The script writes changes to the user's OpenClaw config file (in-place) and updates meta.lastTouchedAt; a backup option exists. This write access is expected for a config-patching tool, but users should be aware it modifies their agent config and should run with --dry-run and/or --backup when first using it.
Assessment
This skill is coherent for its stated purpose, but take normal precautions: run the script with --dry-run first to inspect the proposed changes, use --backup before writing, confirm you supplied the correct group ID and account IDs (the script will raise if an account is missing), and restart/reload your Gateway after changes. The coordinator behavior is enforced by a systemPrompt in config — test both plain messages and @mentions to ensure the bots behave as expected. No network exfiltration or secret access is required by this skill.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ay6ntw1y2n2g5pgmmdtsp4983wx29
117downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0
AlexShen@alex-shen1121
latest
Download

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 NO_REPLY

Quick start

  1. Confirm the group chat ID (oc_xxx) and the Feishu account IDs for all bots.
  2. Decide which bot is the default coordinator, usually company-ceo.
  3. Run scripts/apply_feishu_group_company.py against ~/.openclaw/openclaw.json.
  4. Reload/restart Gateway if needed.
  5. 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 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

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

Comments

Loading comments...