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.