← 返回 Skills 市场
248
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install feishu-bot-manager-twisted
功能描述
交互式添加和管理多个飞书机器人账户,支持账户级和群聊级路由绑定指定 Agent 处理消息。
使用说明 (SKILL.md)
feishu-bot-manager
飞书多账户机器人配置管理 Skill。
路由绑定方案
方案 1:账户级绑定
该飞书账户的所有消息 → 指定 Agent
适用场景:一个机器人专门服务一个 Agent。比如创建一个"销售机器人",它的所有消息都由"销售 Agent"处理。
生成的绑定:
{ "agentId": "recruiter", "match": { "channel": "feishu", "accountId": "bot-sales" } }
方案 2:群聊级绑定
特定群聊的消息 → 指定 Agent
适用场景:把 Agent 绑定到特定群聊。多个机器人在群里,但不同群聊分配给不同 Agent。
生成的绑定:
{ "agentId": "recruiter", "match": { "channel": "feishu", "peer": { "kind": "group", "id": "oc_xxx" } } }
注意:群聊级绑定优先级更高,会覆盖账户级绑定!
使用方式
交互模式(通过对话)
直接说:"添加飞书机器人"
我会询问:
- App ID 和 App Secret
- 账户信息(账户 ID、机器人名称)
- 选择路由绑定方案(账户级/群聊级)
- 选择绑定的 Agent
- 群聊 ID(如果选群聊级绑定)
- 预览确认后执行
命令行调用
# 账户级绑定 - 该机器人所有消息都由指定 Agent 处理
openclaw skills run feishu-bot-manager -- \
--app-id cli_xxx \
--app-secret yyy \
--account-id bot-sales \
--agent-id recruiter \
--routing-mode account
# 群聊级绑定 - 特定群聊的消息由指定 Agent 处理
openclaw skills run feishu-bot-manager -- \
--app-id cli_xxx \
--app-secret yyy \
--account-id bot-sales \
--agent-id recruiter \
--chat-id oc_xxx \
--routing-mode group
参数说明
| 参数 | 必填 | 说明 |
|---|---|---|
| --app-id | ✅ | 飞书 App ID (cli_xxx) |
| --app-secret | ✅ | 飞书 App Secret |
| --account-id | ❌ | 账户标识,默认自动生成 |
| --bot-name | ❌ | 机器人名称,默认 "Feishu Bot" |
| --dm-policy | ❌ | DM 策略: open/pairing/allowlist,默认 open |
| --agent-id | ❌ | 要绑定的 Agent ID |
| --chat-id | ❌ | 群聊 ID (oc_xxx),群聊绑定时需要 |
| --routing-mode | ❌ | 路由模式: account/group,默认 account |
配置结构示例
添加新机器人后,配置会变成这样(保留现有配置):
{
"channels": {
"feishu": {
"enabled": true,
"appId": "cli_现有", // ← 保留不动
"appSecret": "现有Secret", // ← 保留不动
"dmPolicy": "open",
"accounts": { // ← 新添加
"bot-new": {
"appId": "cli_xxx",
"appSecret": "yyy",
"botName": "新机器人",
"dmPolicy": "open",
"allowFrom": ["*"],
"enabled": true
}
}
}
},
"bindings": [
{ // ← 新添加
"agentId": "recruiter",
"match": {
"channel": "feishu",
"accountId": "bot-new" // 或 "peer": { "kind": "group", "id": "oc_xxx" }
}
}
]
}
流程
- 检查并备份现有配置
- 添加新账户到
channels.feishu.accounts - 根据选择的路由模式添加 binding
- 设置
session.dmScope为per-account-channel-peer - 重启 Gateway
注意事项
- 保留现有配置:现有
appId/appSecret完全不动 - 自动备份:修改前自动备份 openclaw.json
- dmScope 设置:自动设置会话绑定颗粒度
- 重启 Gateway:重启后约 10-30 秒恢复服务
- 恢复方法:如出问题可用备份文件手动恢复
安全使用建议
This skill appears to implement a Feishu bot account manager, but review a few issues before installing:
- The code directly reads and writes your OpenClaw config file at ~/.openclaw/openclaw.json and creates backups under ~/.openclaw/backups. The skill metadata did not declare this config-path requirement, so the platform may not warn you. Make sure you have a current manual backup and test in a non-production environment first.
- The skill will store the provided App Secret in your openclaw.json. Only provide secrets you are comfortable storing in that file and verify file permissions.
- The script runs two CLI commands that affect the system: 'openclaw config set session.dmScope ...' and 'openclaw gateway restart'. Expect a Gateway restart (10–30s downtime). Ensure the 'openclaw' CLI is present and you accept the restart.
- The bundled lib/validator.js contains a validation bug: it appears to require peer.id for bindings, which contradicts account-level bindings described in the documentation. This looks like a logic bug (not necessarily malicious) but could cause confusion or false rejections.
- package.json lists an unnecessary external dependency ('readline'), which is odd and suggests the package.json was not carefully curated.
Recommendations: inspect the code yourself (you can read index.js and lib/validator.js), ensure an up-to-date backup of ~/.openclaw/openclaw.json, run the tool in a safe/test instance first, and confirm you are comfortable with storing app secrets in the config. If the author updates metadata to declare the required config path and fixes the validator and package.json oddity, my assessment would be more favorable.
功能分析
Type: OpenClaw Skill
Name: feishu-bot-manager-twisted
Version: 0.0.1
The skill is a legitimate configuration manager for Feishu (Lark) bots within the OpenClaw ecosystem. It automates the process of adding bot credentials to the local `openclaw.json` configuration file, setting up message routing bindings, and restarting the gateway service. The implementation in `index.js` includes proper configuration backup logic and uses standard OpenClaw CLI commands for system updates, with no evidence of data exfiltration, unauthorized remote execution, or malicious prompt injection.
能力评估
Purpose & Capability
The code's behavior (adding Feishu accounts to ~/.openclaw/openclaw.json, creating backups, adding bindings, setting session.dmScope, and restarting the Gateway) matches the skill description. However, the skill metadata declares no required config paths while the code directly reads/writes $HOME/.openclaw/openclaw.json and ~$HOME/.openclaw/backups — this is an inconsistency. package.json lists an npm dependency on 'readline' (a Node builtin) which is unnecessary and unexpected.
Instruction Scope
SKILL.md instructions (interactive prompts and CLI flags for app id/secret, account id, agent id, routing mode) align with index.js. The runtime actions are limited to reading/writing the OpenClaw config and invoking the 'openclaw' CLI to set dmScope and restart the Gateway — all within the documented scope. The skill does not contact external endpoints or exfiltrate data, but it does persist secrets (appSecret) into the config file as expected for this purpose.
Install Mechanism
There is no install spec (instruction-only style), and code files are bundled. That lowers install risk compared with arbitrary downloads. Still, package.json contains an unnecessary external dependency ('readline') which is unusual and may confuse users or installers.
Credentials
The skill expects and manipulates the user's OpenClaw configuration file at ~/.openclaw/openclaw.json but the declared metadata lists no required config paths — the platform won't warn users that the skill will access and change a local config file. The skill legitimately asks for App ID and App Secret (needed for adding a bot) and writes them into the config; that is expected but sensitive. The included validator (lib/validator.js) contains a check that effectively requires binding.match.peer.id for all bindings, which contradicts account-level bindings described in documentation and may lead to false validation errors or confusion.
Persistence & Privilege
The skill is user-invocable and not always-enabled; it does not request persistent platform privileges. It will, however, run 'openclaw config set ...' and 'openclaw gateway restart' which modify runtime behavior and restart a service — appropriate for this tool but potentially disruptive; users should expect the Gateway restart side effects.
如何使用
- 确保已安装 OpenClaw(本地或 Docker 部署)
- 在对话框中输入安装命令:
/install feishu-bot-manager-twisted - 安装完成后,直接呼叫该 Skill 的名称或使用
/feishu-bot-manager-twisted触发 - 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v0.0.1
feishu-bot-manager-twisted 0.0.1
- 初始版本发布,支持多飞书机器人账户的添加与配置管理
- 支持账户级和群聊级两种消息路由绑定方案
- 提供交互式对话和命令行两种添加新飞书机器人的方式
- 自动备份与恢复配置,变更后自动重启 Gateway
- 详细参数选项与用法说明,便于快速部署和调整
元数据
常见问题
Feishu Bot Manager 是什么?
交互式添加和管理多个飞书机器人账户,支持账户级和群聊级路由绑定指定 Agent 处理消息。 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 248 次。
如何安装 Feishu Bot Manager?
在 OpenClaw 或 Claude Code 对话框中运行命令「/install feishu-bot-manager-twisted」即可一键安装,无需额外配置。
Feishu Bot Manager 是免费的吗?
是的,Feishu Bot Manager 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。
Feishu Bot Manager 支持哪些平台?
Feishu Bot Manager 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(cross-platform)。
谁开发了 Feishu Bot Manager?
由 TwistedCz(@twistedcz)开发并维护,当前版本 v0.0.1。
推荐 Skills