add-telegram-swarm
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Best for Multi-agent Telegram integr…Works with GitHub
⌘source
- author
@qwibitai- language
- TypeScript
★27kstars
12kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Adds multiple bot identities to a Telegram group for agent teams
- ·Assigns a unique bot per subagent for visual distinction
- ·Uses pool bots for send-only message delivery
- ·Renames bots dynamically to match subagent roles
- ·Requires existing Telegram channel setup via /add-telegram
Use Cases
- →Running a team of specialized agents in a Telegram group where each agent's messages are visually distinct
- →Managing a multi-agent system where users need to identify which agent is responding in a chat
- →Deploying a swarm of bots for a collaborative project in a Telegram channel
Best for
- ✓Multi-agent Telegram integrations
- ✓Teams requiring clear agent attribution in chat
Not ideal for
- !Single-bot Telegram setups
- !Projects without existing Telegram channel configuration
FAQs
name
add-telegram-swarm
description
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Add Agent Swarm to Telegram
This skill adds Agent Teams (Swarm) support to an existing Telegram channel. Each subagent in a team gets its own bot identity in the Telegram group, so users can visually distinguish which agent is speaking.
Prerequisite: Telegram must already be set up via the /add-telegram skill. If src/telegram.ts does not exist or TELEGRAM_BOT_TOKEN is not configured, tell the user to run /add-telegram first.
How It Works
- The main bot receives messages and sends lead agent responses (already set up by
/add-telegram) - Pool bots are send-only — each gets a Grammy
Apiinstance (no polling) - When a subagent calls
send_messagewith asenderparameter, the host assigns a pool bot and renames it to match the sender's role - Messages appear in Telegram from different bot identities
Subagent calls send_message(text: "Found 3 results", sender: "Researcher")
→ MCP writes IPC file with sender field
→ Host IPC watcher picks it up
→ Assigns pool bot #2 to "Researcher" (round-robin, stable per-group)
→ Renames pool bot #2 to "Researcher" via setMyName
→ Sends message via pool bot #2's Api instance
$install
1-click copynpx skills add qwibitai/nanoclaw --skill add-telegram-swarmSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.