OpenClaw Async Telegram Bot Skill

English | 简体中文

Scale one OpenClaw into a multi-bot Telegram fleet in minutes.

This skill automates Telegram bot onboarding with guardrails:

• validates tokens with Telegram getMe
• enforces username policy Nebutra###_bot
• requires fresh token for new-bot flow (no silent reuse of old tokens)
• auto-maps bot naming to Greek philosopher identities
• wires bots into OpenClaw accounts
• restarts and health-checks gateway automatically
• can spawn one isolated agent per bot for parallel workflows

Install in 10 Seconds

npx skills add https://github.com/Nebutra/OpenClaw-Async-Telegram-Bot-Skill --skill openclaw-async-telegram-bot

Alternative discovery pages:

• Smithery: https://smithery.ai/skills/nebutra/openclaw-async-telegram-bot-skill
• Skills directory: https://skills.sh/nebutra/openclaw-async-telegram-bot-skill/openclaw-async-telegram-bot

Quick Start

Note: botfather_rpa_assist_mac.sh requires macOS Accessibility permission for your terminal app (System Settings -> Privacy & Security -> Accessibility).

# Option A (macOS): RPA-assisted flow
bash scripts/botfather_rpa_assist_mac.sh --name "Aristotle"

# Option B (cross-platform): planning + manual BotFather step
# 1) Generate BotFather new-bot plan (name + username + next serial)
bash scripts/prepare_botfather_new_bot.sh

# 2) Create the bot in BotFather with generated values and copy fresh token

# add/update one Telegram bot account
bash scripts/add_async_telegram_bot.sh --token "<BOTFATHER_TOKEN>"

# add bot + create isolated agent bound to this account
bash scripts/add_async_telegram_bot.sh --token "<BOTFATHER_TOKEN>" --agent-id "plato-agent"

Command Reference

# macOS RPA-assisted flow (open BotFather + send /newbot + configure OpenClaw)
bash scripts/botfather_rpa_assist_mac.sh --name "Aristotle"

# macOS RPA-only (no configure yet)
bash scripts/botfather_rpa_assist_mac.sh --name "Aristotle" --no-configure

# adjust clipboard wait window (seconds)
bash scripts/botfather_rpa_assist_mac.sh --name "Aristotle" --wait-clipboard 300

# planning helper for BotFather flow
bash scripts/prepare_botfather_new_bot.sh

# planning helper with forced serial and name
bash scripts/prepare_botfather_new_bot.sh --serial 2 --name "Aristotle"

# planning helper JSON output for automation
bash scripts/prepare_botfather_new_bot.sh --json

# force account id
bash scripts/add_async_telegram_bot.sh --token "<TOKEN>" --account-id "plato-007"

# force display name
bash scripts/add_async_telegram_bot.sh --token "<TOKEN>" --name "Plato"

# dry run only
bash scripts/add_async_telegram_bot.sh --token "<TOKEN>" --dry-run

# skip gateway restart
bash scripts/add_async_telegram_bot.sh --token "<TOKEN>" --skip-restart

# use a different model when creating agent
bash scripts/add_async_telegram_bot.sh --token "<TOKEN>" --agent-id "plato-agent" --model "MiniMax-M2.5"

# intentionally reuse a token already registered in OpenClaw (update flow only)
bash scripts/add_async_telegram_bot.sh --token "<TOKEN>" --allow-existing-token

Safety and Policy

• Username must match: ^Nebutra[0-9]{3}_bot$
• Token must pass Telegram API validation
• New bot flow must use a fresh BotFather token
• Health checks must pass: running=true and probe.ok=true
• Prevents account-id collisions with existing bot IDs

Repository Layout

• SKILL.md - trigger rules + workflow for agent execution
• scripts/botfather_rpa_assist_mac.sh - macOS RPA assistant for BotFather + OpenClaw configuration
• scripts/prepare_botfather_new_bot.sh - assisted new-bot planning for BotFather
• scripts/add_async_telegram_bot.sh - production onboarding script

Requirements

• openclaw
• curl
• jq

License

MIT