Agent skill

Telegram Bot Manager

Manage and configure Telegram bots for OpenClaw. An agent skill from CraftOS-dev/CraftBot.

MITAuto-check passedProductivity & Automation

Install Telegram Bot Manager

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot telegram-bot-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/telegram-bot-manager .claude/skills/telegram-bot-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "telegram-bot-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/telegram-bot-manager into .claude/skills/telegram-bot-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram-bot-manager", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/CraftOS-dev/CraftBot/tree/main/skills/telegram-bot-manager

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot telegram-bot-manager --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/telegram-bot-manager .agents/skills/telegram-bot-manager && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "telegram-bot-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/telegram-bot-manager into .agents/skills/telegram-bot-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram-bot-manager", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot telegram-bot-manager --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/telegram-bot-manager .cursor/skills/telegram-bot-manager && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "telegram-bot-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/telegram-bot-manager into .cursor/skills/telegram-bot-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram-bot-manager", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/CraftOS-dev/CraftBot.git --path skills/telegram-bot-manager

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot telegram-bot-manager --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/telegram-bot-manager .gemini/skills/telegram-bot-manager && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "telegram-bot-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/telegram-bot-manager into .gemini/skills/telegram-bot-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram-bot-manager", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot telegram-bot-manager

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/telegram-bot-manager .github/skills/telegram-bot-manager && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "telegram-bot-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/telegram-bot-manager into .github/skills/telegram-bot-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram-bot-manager", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install CraftOS-dev/CraftBot telegram-bot-manager --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/telegram-bot-manager .opencode/skills/telegram-bot-manager && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "telegram-bot-manager" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/telegram-bot-manager into .opencode/skills/telegram-bot-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telegram-bot-manager", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: telegram-bot-manager
GitHub stars: 392
Token cost: ~836 tokens
SKILL.md length: 309 words
Files: 11 (incl. scripts, references)
Skills in repo: 89
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manage and configure Telegram bots for OpenClaw. An agent skill from CraftOS-dev/CraftBot.

Works in 2 steps: Create bot via BotFather → Configure in OpenClaw
Setting up Telegram integrations
SKILL.md covers Quick Start, Common Workflows, Bot Commands Reference and Webhook vs Polling, plus 3 more sections
Runs Python scripts from its folder; calls curl; reaches api.telegram.org and telegram.org

What it does

Telegram Bot Manager is an agent skill from CraftOS-dev/CraftBot. Manage and configure Telegram bots for OpenClaw. Use when setting up Telegram integrations, troubleshooting bot connectivity, configuring bot tokens, or managing Telegram channel/webhook settings. Handles bot registration, token validation, and network connectivity checks for api.telegram.org.

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts and reference files (for example `QUICKSTART.md`, `README.md` and `RELEASE_NOTES.md`).

It sits in Productivity & Automation, covering Chatbots and conversational support and Webhooks. It works with Telegram. The repository describes itself as: One agent. Every kind of work. The licence is MIT.

When your agent uses it

Setting up Telegram integrations
Troubleshooting bot connectivity
Configuring bot tokens
Managing Telegram channel/webhook settings

Example prompts

“/telegram-bot-manager”

Requirements

Python 3
A credential in YOUR_TOKEN

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

Create bot via BotFather
Configure in OpenClaw

What it can do on your machine

Read from SKILL.md and the folder at commit b50970c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- api.telegram.org
- telegram.org
Also links to:
- core.telegram.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Telegram Bot Manager loads about 836 tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 309 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~79
When it runs · the whole SKILL.md, loaded when a task matches: ~836
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from CraftOS-dev/CraftBot at commit b50970c, republished under its MIT licence (© CraftOS-dev). 309 words, ~836 tokens.

Download SKILL.mdSave it as .claude/skills/telegram-bot-manager/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.

name: telegram-bot-manager
description: Manage and configure Telegram bots for OpenClaw. Use when setting up Telegram integrations, troubleshooting bot connectivity, configuring bot tokens, or managing Telegram channel/webhook settings. Handles bot registration, token validation, and network connectivity checks for api.telegram.org.

Telegram Bot Manager

Quick Start

Setup a new Telegram bot

Create bot via BotFather
- Message @BotFather on Telegram
- Use /newbot command
- Follow prompts for bot name and username
- Copy the bot token (format: 1234567890:ABCdefGHIjklMNOpqrsTUVwxyz)
Configure in OpenClaw
- Add token to OpenClaw config
- Enable Telegram plugin
- Set up pairing mode for DM access

Validate bot configuration

bash

# Test Telegram API connectivity
curl -I https://api.telegram.org

# Check bot token validity
curl -s "https://api.telegram.org/bot<YOUR_TOKEN>/getMe"

Common Workflows

Troubleshooting connectivity issues

When api.telegram.org is unreachable:

Check network access
bash
```
curl -I -m 10 https://api.telegram.org
```
Verify DNS resolution
bash
```
nslookup api.telegram.org
```
Test alternative endpoints
bash
```
curl -I https://telegram.org
```

Configuring OpenClaw Telegram integration

See OPENCLAW_CONFIG.md for detailed configuration steps.

Bot token security

Never commit bot tokens to version control
Store tokens in environment variables or secure config files
Rotate tokens if compromised
Use different tokens for different environments (dev/prod)

Bot Commands Reference

Common Telegram bot commands for BotFather:

/newbot - Create a new bot
/mybots - Manage your bots
/setdescription - Set bot description
/setabouttext - Set about text
/setuserpic - Set bot profile picture
/setcommands - Set bot commands
/token - Generate new token
/revoke - Revoke current token
/setprivacy - Configure privacy mode

Webhook vs Polling

Webhook (Recommended for production)

Bot receives updates via HTTP POST
Requires public HTTPS endpoint
More efficient for high-volume bots

Polling (Good for development)

Bot continuously checks for updates
Simpler setup, no public endpoint needed
Easier to debug locally

See WEBHOOK_SETUP.md for webhook configuration.

Error Handling

Common errors and solutions

"Connection timed out"

Check firewall rules
Verify proxy configuration
Test with different network

"Invalid token"

Verify token format (should contain colon)
Check for extra spaces or characters
Regenerate token if needed

"Bot not responding"

Verify bot is not blocked
Check bot privacy settings
Ensure bot has proper permissions

Testing Your Bot

Manual testing

Search for your bot username on Telegram
Start a conversation with /start
Test basic commands

Automated testing

Use the test script in scripts/test_bot.py for automated validation.

References

Files

SKILL.md and 10 other files (scripts, references) in skills/telegram-bot-manager of CraftOS-dev/CraftBot.

SKILL.md
QUICKSTART.md
README.md
RELEASE_NOTES.md
_meta.json
metadata.json
references/OPENCLAW_CONFIG.md
references/WEBHOOK_SETUP.md
scripts/package_skill.py
scripts/setup_bot.py
scripts/test_bot.py

Open the folder on GitHubat commit b50970c

Compare with similar skills

Telegram Bot Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Telegram Bot Manager compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Telegram Bot Manager this skillCraftOS-dev/CraftBot	392	—	~836	Automated safety check: Pass	MIT	today
Telegram Bot Builderaiskillstore/marketplace	430	3 repos	~2.2k	Automated safety check: Notes	None	today
Whatsapp Telegramericrisco/rsc-harness	156	—	~2.9k	Automated safety check: Pass	MIT	today
Chat SDKdatabuddy-analytics/Databuddy	1.2k	—	~2.6k	Automated safety check: Pass	AGPL-3.0	today
Tg Bot Opsserejaris/personal-corp-os	229	—	~1.6k	Automated safety check: Notes	MIT	3 days ago
Telegram Setupvellum-ai/vellum-assistant	1.4k	—	~2.9k	Automated safety check: Warn	MIT	3 days ago

Similar skills

Telegram Bot Builder
aiskillstore/marketplace
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots.
430 GitHub starsUsed in 3 repos~2.2k tokens
Productivity & AutomationAuto-check: notes
Whatsapp Telegram
ericrisco/rsc-harness
A skill your agent uses when wiring an app or agent to message customers over the WhatsApp Cloud API or a Telegram bot — order updates, OTP codes, reminders, alerts and broadcasts — or when…
156 GitHub stars~2.9k tokensUpdated today
Backend & APIsAuto-check passed
Chat SDK
databuddy-analytics/Databuddy
Build multi-platform chat bots with Chat SDK (chat npm package).
1.2k GitHub stars~2.6k tokensUpdated today
Agent WorkflowsAuto-check passed
Tg Bot Ops
serejaris/personal-corp-os
A skill your agent uses when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway.
229 GitHub stars~1.6k tokensUpdated 3 days ago
Backend & APIsAuto-check: notes
Telegram Setup
vellum-ai/vellum-assistant
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage
1.4k GitHub stars~2.9k tokensUpdated 3 days ago
Backend & APIsAuto-check: warnings
Pytdbot
pytdbot/client
Write Telegram bots and userbots with Pytdbot (async TDLib wrapper with high-level helpers; not the Telegram Bot API).
137 GitHub stars~4.3k tokensUpdated 9 days ago
Productivity & AutomationAuto-check passed

Questions about Telegram Bot Manager

What does Telegram Bot Manager do?

Manage and configure Telegram bots for OpenClaw. An agent skill from CraftOS-dev/CraftBot. Telegram Bot Manager is an agent skill from CraftOS-dev/CraftBot. Manage and configure Telegram bots for OpenClaw.

When should I use Telegram Bot Manager?

Telegram Bot Manager fits situations like: setting up Telegram integrations; troubleshooting bot connectivity; configuring bot tokens; managing Telegram channel/webhook settings.

How do I install Telegram Bot Manager in Claude Code?

Run `npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a claude-code`. Or copy the skill folder (skills/telegram-bot-manager in CraftOS-dev/CraftBot) into .claude/skills/telegram-bot-manager in your project. Claude Code loads it when a task matches its description.

How do I install Telegram Bot Manager in Codex?

Run `npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a codex`. Or copy the skill folder (skills/telegram-bot-manager in CraftOS-dev/CraftBot) into .agents/skills/telegram-bot-manager in your project. Codex loads it when a task matches its description.

Can I use Telegram Bot Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CraftOS-dev/CraftBot --skill telegram-bot-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/telegram-bot-manager, .gemini/skills/telegram-bot-manager, .github/skills/telegram-bot-manager and .opencode/skills/telegram-bot-manager in your project.

What does Telegram Bot Manager need to run?

Going by SKILL.md and its folder, Telegram Bot Manager needs Python for the scripts in its folder and the command-line tools its instructions call (curl). Our summary lists: Python 3; A credential in YOUR_TOKEN.

Does Telegram Bot Manager access the network?

SKILL.md names 3 domains. In commands or code: api.telegram.org and telegram.org; the agent is likely to contact these when it follows the instructions. As links in the text: core.telegram.org. This is read from the text; nothing was executed.

Is Telegram Bot Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Telegram Bot Manager use?

Telegram Bot Manager is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Telegram Bot Manager use?

About 836 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Telegram Bot Manager?

Skills that share tags, products or a category with Telegram Bot Manager: Telegram Bot Builder (aiskillstore/marketplace, 430 stars), Whatsapp Telegram (ericrisco/rsc-harness, 156 stars), Chat SDK (databuddy-analytics/Databuddy, 1.2k stars) and Tg Bot Ops (serejaris/personal-corp-os, 229 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Telegram Bot Manager?

CraftOS-dev (a GitHub user) maintains it in CraftOS-dev/CraftBot, which has 392 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 7, 2026.

Source: CraftOS-dev/CraftBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Telegram Bot Manager

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Telegram Bot Manager

Quick Start

Setup a new Telegram bot

Validate bot configuration

Common Workflows

Troubleshooting connectivity issues

Configuring OpenClaw Telegram integration

Bot token security

Bot Commands Reference

Webhook vs Polling

Webhook (Recommended for production)

Polling (Good for development)

Error Handling

Common errors and solutions

Testing Your Bot

Manual testing

Automated testing

References

Files

Compare with similar skills

Similar skills

More from CraftOS-dev/CraftBot

Related

Questions about Telegram Bot Manager