add-telegram-swarm

Configure Telegram bot pools to present subagents as distinct identities.

85|23|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/DingyangLyu/MatClaw --skill add-telegram-swarm-dingyanglyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-telegram-swarm
Source: https://github.com/DingyangLyu/MatClaw/tree/main/.claude/skills/add-telegram-swarm
Command: npx skills add https://github.com/DingyangLyu/MatClaw --skill add-telegram-swarm-dingyanglyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MatClaw agent teams (subagents) all appear from the same Telegram bot identity, making it hard for users to distinguish who is speaking in group chats; this Skill enables each subagent to present as a separate bot identity so messages are clearly attributed and scannable.

Core Features & Use Cases

  • Adds a send-only pool of Telegram bots (pool APIs) so each subagent can send messages from a distinct bot identity in group chats.
  • Routes MCP send_message calls that include a sender parameter through the pool, renames pool bots to match roles, and preserves stable per-group sender→bot assignments with round-robin and fallback behavior.
  • Use cases: collaborative multi-agent simulations, demonstrative agent teams in user groups, or any workflow where role-distinct messaging improves clarity and UX.

Quick Start

Set up agent teams in my Telegram group by supplying pool bot tokens, adding them to the group with group privacy disabled, and running the add-telegram-swarm configuration steps.

Frequently Asked Questions about add-telegram-swarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make multi-agent subagents show as separate Telegram bot identities in a group chat?

To make subagents show as separate Telegram bot identities, you can configure a send-only bot pool with distinct tokens and route messages via an IPC sender parameter. This allows each subagent to send messages from a distinct bot identity in group chats.

Why do all my multi-agent subagents appear as the same Telegram bot in group chats?

Multi-agent subagents appear as the same Telegram bot because they share a single bot identity by default. Applying a bot pool configuration assigns distinct visual identities to each subagent, making messages clearly attributed and scannable.

What do I need to set up a Telegram bot pool for multi-agent messaging?

To set up a Telegram bot pool for multi-agent messaging, you need to supply multiple Telegram bot tokens, add those bots to your group with group privacy disabled, and initialize send-only Grammy API instances for routing.

Does the Telegram agent swarm bot pool support round-robin assignment and fallback behavior?

Yes, the Telegram agent swarm bot pool supports stable per-group sender-to-bot assignments using round-robin routing. It also includes fallback behavior to handle cases where the configured bot pool is exhausted.

Can I use this Telegram bot pool configuration with any multi-agent framework?

This Telegram bot pool configuration applies specifically to MatClaw-hosted Telegram integrations where teams of subagents need separate visual identities. It requires updating IPC routing to accept a sender parameter for role-distinct messaging.