Openclaw-master-skills telegram

OpenClaw skill for designing Telegram Bot API workflows and command-driven conversations using direct HTTPS requests (no SDKs).

install

source · Clone the upstream repo

git clone https://github.com/LeoYeAI/openclaw-master-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/LeoYeAI/openclaw-master-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/telegram" ~/.claude/skills/leoyeai-openclaw-master-skills-telegram && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/LeoYeAI/openclaw-master-skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/telegram" ~/.openclaw/skills/leoyeai-openclaw-master-skills-telegram && rm -rf "$T"

manifest: skills/telegram/SKILL.md

Telegram Bot Skill (Advanced)

Purpose

Provide a clean, production-oriented guide for building Telegram bot workflows via the Bot API, focusing on command UX, update handling, and safe operations using plain HTTPS.

Best fit

You want a command-first bot that behaves professionally.
You need a reliable update flow (webhook or polling).
You prefer direct HTTP calls instead of libraries.

Not a fit

You require a full SDK or framework integration.
You need complex media uploads and streaming in-process.

Quick orientation

Read
```
references/telegram-bot-api.md
```
for endpoints, update types, and request patterns.

Read

references/telegram-commands-playbook.md

for command UX and messaging style.

Read
```
references/telegram-update-routing.md
```
for update normalization and routing rules.

Read

references/telegram-request-templates.md

for HTTP payload templates.

Keep this SKILL.md short and use references for details.

Required inputs

Bot token and base API URL.
Update strategy: webhook or long polling.
Command list and conversation tone.
Allowed update types and rate-limit posture.

Expected output

A clear command design, update flow plan, and operational checklist.

Operational notes

Prefer strict command routing:
```
/start
```
,
```
/help
```
,
```
/settings
```
,
```
/status
```
.
Always validate incoming update payloads and chat context.
Handle 429s with backoff and avoid message bursts.

Security notes

Never log tokens.
Use webhooks with a secret token header when possible.