360 Secure SkillHub
360 安全技能中心

Telegram

该技能提供生产级Telegram Bot开发指引,聚焦命令式交互、更新处理与安全操作,采用纯HTTPS请求无需SDK。适合需构建命令优先的专业机器人、需要可靠webhook/轮询更新流、偏好直接HTTP调用的场景;不适合需SDK集成或复杂媒体上传的需求。输入需Bot令牌、更新策略、命令列表等,输出为命令设计、更新流计划及操作清单。

codedao12
codedao12
热度 99.85
最近更新 2026-05-11 15:52:26
分类:开发依赖:纯提示词应用场景:API 集成 / 工作流 / 模板

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add telegram
Metadata
name
telegram
description
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.