openclaw-telegram-subagents

English

A practical OpenClaw skill for putting multiple agents onto Telegram using separate bot accounts, with evidence-based routing validation on OpenClaw 2026.3.2.

What It Teaches

This skill teaches OpenClaw how to:

• add a Telegram sub-account such as luna,
• bind that account to an independent agent,
• verify outbound and inbound routing, and
• avoid false-positive success claims from config writes or restarts alone.

It is useful when one OpenClaw gateway hosts multiple Telegram bots and each bot should map to a different agent.

Included Skill

• skills/openclaw-telegram-subagents/SKILL.md

Suggested Trigger Examples

• "Set up a Telegram sub-agent bot in OpenClaw"
• "Put a child agent on Telegram with its own bot token"
• "Configure Telegram multi-bot multi-agent routing in OpenClaw 2026.3.2"
• "Bind the luna Telegram account to a separate OpenClaw agent"

Install

Copy the skills/openclaw-telegram-subagents/ directory into your OpenClaw skills location.

Example:

~/.openclaw/workspace/skills/openclaw-telegram-subagents/

Notes

This skill keeps a strict validation stance:

• config write success is not deployment success,
• service restart success is not deployment success,
• full success requires inbound routing proof to the target agent.

---

中文

这是一个实用的 OpenClaw 技能，用来把多个 agent 通过不同的 Telegram bot 账号部署到 Telegram 上，并在 OpenClaw 2026.3.2 上使用基于证据的方式验证路由是否真的生效。

它会教什么

这个技能会教 OpenClaw：

• 如何添加一个 Telegram 子账号，比如 luna
• 如何把这个账号绑定到独立 agent
• 如何验证出站和入站路由
• 如何避免把“配置写入成功”或“重启成功”误判成“部署已经成功”

适用场景是：

• 一个 OpenClaw gateway 同时挂多个 Telegram bot
• 每个 bot 都需要对应不同的 agent

包含的技能文件

• skills/openclaw-telegram-subagents/SKILL.md

触发示例

• “给 OpenClaw 配一个 Telegram 子 agent bot”
• “把一个子 agent 放到 Telegram 上，用独立 bot token”
• “在 OpenClaw 2026.3.2 里配置 Telegram 多 bot 多 agent 路由”
• “把 luna 这个 Telegram account 绑定到独立 OpenClaw agent”

安装方式

把 skills/openclaw-telegram-subagents/ 目录复制到你的 OpenClaw skills 目录。

例如：

~/.openclaw/workspace/skills/openclaw-telegram-subagents/

说明

这个技能会坚持严格验收：

• 配置写入成功，不等于部署成功
• 服务重启成功，不等于部署成功
• 只有确认入站消息真的路由到目标 agent，才能算完整成功