ClawHub

Telegram Bot API

v1.0.0

Build Telegram bots with correct API calls, message formatting, keyboards, and webhook setup.

⭐ 0· 523·2 current·2 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (Telegram Bot API helper) match the contents: comprehensive docs, curl examples, webhook/polling guidance, keyboard/media handling. The only required binary is curl and the only external endpoint used is api.telegram.org, which is appropriate for this purpose.
ℹ
Instruction Scope
Instructions explicitly tell the agent to save bot configuration and tokens under ~/telegram-bot-api/ (but only with explicit user permission). This is expected for a helper that manages bot tokens, but users should be aware the skill suggests persisting secrets locally and should only permit that if they trust the environment. Other instructions remain scoped to Telegram API usage and local config.
✓
Install Mechanism
No install spec or downloads — instruction-only with examples. Nothing is written to disk by an installer; only recommended local files are in the user's home directory (and only when the user consents).
ℹ
Credentials
The skill declares no required environment variables or credentials. Examples use a ${TOKEN} placeholder and scripts that expect a token; storing a bot token is required for operation but the skill asks for permission before saving. This is proportionate, but confirm how/where you want secrets stored (env vars, secret manager, or the suggested home dir).
✓
Persistence & Privilege
always:false and normal invocation settings. The only persistence is optional local files under the user's home directory for bot configs and templates; the skill does not request system-wide changes or modify other skills' settings.
Assessment
This skill is an instruction-only Telegram Bot API guide and is internally consistent. Key points before installing/using: 1) The skill may ask to save your bot token to ~/telegram-bot-api/bots/{name}.md — only allow this if you trust the environment and the machine's filesystem; prefer using a secrets manager or environment variables if you prefer. 2) Never paste your bot token into public chat or logs; if you suspect it was exposed, regenerate it with @BotFather. 3) Webhook examples require exposing an HTTPS endpoint (ngrok/cloudflared); be careful when exposing localhost to the public. 4) The skill's examples reference ${TOKEN} but it does not require any platform-level credentials — the token is a Telegram credential you provide. 5) Because this is instruction-only, there is no installer, no external downloads, and the repo contained only documentation — that reduces risk. If the skill later asked to run downloaded code, contact external endpoints other than api.telegram.org, or required unrelated credentials (AWS, GitHub tokens, etc.), reconsider or mark as suspicious.

Like a lobster shell, security has layers — review code before you run it.

latestvk9761wvzvay90t5t6hzp9fsqqs81reev

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🤖 Clawdis
OSLinux · macOS · Windows
Binscurl

Comments