
Add Telegram Channel
Lets your NanoClaw agent send and receive messages through a Telegram bot.
- Repository
- nanocoai/nanoclaw
- Stars
- 31,072
- Licence
- MIT
- Files
- 3 files
What it does
It adds Telegram as a messaging channel for NanoClaw, so you can chat with your agent through a Telegram bot. The skill copies the Telegram adapter and its tests from the project's channels branch, registers them, installs a pinned adapter package, and walks you through creating a bot with BotFather and saving its token in your .env file. It can also add a second bot under a separate name.
Great for
- Developers running NanoClaw who want to reach their agent from Telegram
- Users who already have a NanoClaw install and want a second Telegram bot alongside an existing one
Skip it if
- People who have never set up NanoClaw, because it assumes an existing install with a build step and pnpm available
- Anyone who wants a non-Telegram channel, since this only covers Telegram
- Users who do not want a bot token stored in .env, because the skill writes the token there and syncs it to the container
Try asking
- “Add Telegram support to my NanoClaw agent”
- “Connect a second Telegram bot to my existing NanoClaw install”
- “Walk me through creating a Telegram bot and pairing it with NanoClaw”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 3 original files, the MIT licence and an attribution note.
add-telegram.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip add-telegram.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip add-telegram.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Turn off Group Privacy in BotFather if you plan to use the bot in group chats, so it sees all messages rather than only mentions.
- Keep the bot token private; the skill stores it in .env and syncs it to the container, so do not commit .env to version control.
- Run the skill on a clean install first, and check the focused tests pass before relying on the bot for real messages.
What's inside
- apply-fixtures.json
- REMOVE.md
- SKILL.md
Redistributed unmodified from nanocoai/nanoclaw under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.