What problem does it solve?
Many multi-agent workflows in Telegram appear as a single bot, making it hard for users to distinguish which subagent produced each message. This Skill makes subagents appear as distinct bot identities in Telegram groups so team outputs are clear, scannable, and attributable.
Core Features & Use Cases
- Multi-bot agent teams: Assign subagents to a pool of send-only Telegram bots that are renamed to match agent roles so messages appear from separate identities.
- Stable per-group mapping and fallbacks: Round-robin assignment with stable sender→bot mapping during runtime and fallback to the main bot if no pool is configured.
- Integration points: Adds TELEGRAM_BOT_POOL environment support, initializes Grammy Api instances for pool bots, extends the MCP send_message tool with a sender parameter, and routes IPC messages through the pool.
- Use Case: Run a researcher+coder agent team in a single Telegram group where each agent posts concise, role-labeled updates via dedicated bot identities.
Quick Start
Ask the assistant to enable multi-bot agent teams for your Telegram group by providing the pool bot tokens and confirming the target group folder.