mirror of https://github.com/LeoYeAI/openclaw-master-skills.git synced 2026-07-27 22:15:43 +00:00

Files

T

MyClaw AI 3e83cee039 feat: expand to 339+ curated skills (v0.3.0)

- Added 175 new high-quality skills across all categories
- 14 distinct categories: AI, Search, Productivity, Dev, Marketing, Media, Finance, Communication, Smart Home, Memory, Security, Data, Social, Other
- Updated all language READMEs and SKILL.md
- Weekly update by MyClaw.ai

2026-03-11 11:54:00 +00:00

1.7 KiB

Raw Blame History

name, description

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

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.

1.7 KiB Raw Blame History