add-telegram
Skill1 starsChanged 7 months agoMITView on GitHub
Add Telegram channel to IronClaw — guides through bot creation, token configuration, and verification
- Reads credentials
16 other projects use a version of this.
Adopted by
Most recently taken up by
- nanocoai/nanoclawtheir own version, first seen Nov 15, 2026
- ss2code/nanoclaw-opstheir own version, first seen Oct 15, 2026
- prathish-ks/isthmustheir own version, first seen Oct 12, 2026
- juancruzmunozalbelo/swarmclawtheir own version, first seen Oct 8, 2026
- gavrielc/nanoclawtheir own version, first seen Oct 8, 2026
- qwibitai/nanoclawtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use add-anydoc, add-clidash and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
TomGranotSkilladd-anydoc
Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.
Also in 5 projects that use this
TomGranotSkilladd-clidash
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
Also in 5 projects that use this
juancruzmunozalbeloSkilladd-voice-transcription
Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.
Also in 5 projects that use this
b1rdmaniaSkillmigrate-memory
Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.
Also in 7 projects that use this
juancruzmunozalbeloSkilladd-telegram-swarm
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Also in 6 projects that use this
jaypylesSkilladd-gmail
Add Gmail integration to NanoClaw. Can be configured as a tool (agent reads/sends emails when triggered from Discord) or as a full channel (emails can trigger the agent, schedule tasks, and receive replies). Guides through GCP OAuth setup and implements the integration.
Also in 5 projects that use this
- +5 more from TomGranot
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Runchuan-BU/BioClaw★ 405same name
- DingyangLyu/MatClaw★ 98same name
- b1rdmania/ghostclaw★ 91same name
- microsoft/amplifier-app-nanoclaw★ 5same name
- 0-CYBERDYNE-SYSTEMS-0/FFT_nano★ 4same name
- TomGranot/groupguard★ 3same name
- prathish-ks/isthmus★ 2same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- add-agentSkill
- add-remote-accessSkill
- configureSkill
- resetSkill
- security-auditSkill
- setupSkill
- startSkill
- stopSkill
- switch-agentSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Add both values to .env:
- Distinctive: line 34
If the gateway is running, restart it to pick up the new env vars
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/add-telegram — Add Telegram Channel
Guide the user through connecting a Telegram bot to IronClaw.
Step 1: Create a Telegram Bot
- Tell the user to open Telegram and message @BotFather
- Send
/newbotto BotFather - Choose a name (e.g., "IronClaw") and username (e.g., "ironclaw_bot")
- Copy the bot token that BotFather provides
Step 2: Get Your Telegram User ID
- Tell the user to message @userinfobot on Telegram
- It will reply with their user ID (a number like 123456789)
- This is needed so IronClaw knows which Telegram user is the operator
Step 3: Configure Environment
- Add both values to
.env:TELEGRAM_BOT_TOKEN=<bot-token-from-botfather> TELEGRAM_OPERATOR_ID=<your-user-id> - Remind the user that
.envis in.gitignore
Step 4: Start the Gateway
- If the gateway is running, restart it to pick up the new env vars
- Start with:
pnpm start:gateway - Also start the runtime worker in another terminal:
pnpm start:runtime - The gateway should show
[telegram] Bot started (polling)
Step 5: Verify
- Open Telegram and find the bot by its username
- Send
/start— should get a welcome message - Send a message like "Hello!" — should get a response from IronClaw
- The response comes from the same agent with the same memory and tools
Step 6: DM Pairing (for other users)
Explain the pairing flow:
- Another user messages the bot and sends
/pair - They get a 6-digit pairing code
- The operator sends
/approve <code>to the bot to approve them - Once approved, the user can chat with the bot in their own DM session
Notes
- Long polling is used for local development (no public URL needed)
- For production, set
TELEGRAM_WEBHOOK_URLin.envto use webhooks instead - The operator's messages go to the "main" session (same as CLI)
- Other users' DMs create separate
dm:telegram:<userId>sessions - Group chats create
group:telegram:<chatId>sessions
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

