agentleFS
tjg37tjg37/ironclaw/.claude/skills/add-telegram/SKILL.md

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

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.
  • TomGranotSkill

    add-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

  • TomGranotSkill

    add-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

  • juancruzmunozalbeloSkill

    add-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

  • b1rdmaniaSkill

    migrate-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

  • juancruzmunozalbeloSkill

    add-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

  • jaypylesSkill

    add-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

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
  1. Very specific:

    Add both values to .env:

    line 25
  2. Distinctive:

    If the gateway is running, restart it to pick up the new env vars

    line 34

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/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 /newbot to 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 .env is 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_URL in .env to 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.