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· 85·0 current·0 all-time
byAlexShen@alex-shen1121
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
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

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments