技能库智客分类：设计创意 telegram OpenClaw

OpenClaw技能用于设计Telegram Bot API工作流程并使用直接的HTTPS请求(没有SDKs)进行命令驱动的对话.

668 安装量 · 29 星标

官方网址：ClawHub

技能介绍

先看中文介绍；官方 description 原文单独保留，不改写 SKILL.md。

做什么

OpenClaw技能用于设计Telegram Bot API工作流程并使用直接的HTTPS请求(没有SDKs)进行命令驱动的对话.

何时用

官方 description 未单独写出 Use when。按规范，代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露：启动时只加载 name 与 description（约 100 token）；任务匹配后才读入整份 SKILL.md 正文；scripts/、references/、assets/ 仅在需要时再读。本文件正文结构：Telegram Bot Skill (Advanced)、Purpose、Best fit、Not a fit、Quick orientation、Required inputs。

文件分析

文件分析：除 SKILL.md 外，正文引用了 references/telegram-bot-api.md、references/telegram-commands-playbook.md、references/telegram-update-routing.md、references/telegram-request-templates.md，属于带资源的技能包，这些文件按需再读。

官方 description（原文）

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

Telegram Bot Skill (Advanced)PurposeBest fitNot a fitQuick orientationRequired inputsExpected outputOperational notesSecurity notes

来源分类：ClawHub Telegram

来源与网址

市场来源：ClawHub

开源榜 Skill 分类

SKILL.md 与 Agent 调用

官方规范 ↗

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

发现技能客户端向 Agent 提供名称与描述目录。
匹配与调用用户指定或任务匹配后，载入 SKILL.md 指令。
按需加载按步骤读取参考文档、使用脚本与素材。

指令中引用的文件 · 4

references/telegram-bot-api.md
references/telegram-commands-playbook.md
references/telegram-update-routing.md
references/telegram-request-templates.md

以下路径提取自原文；文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围，保留技能包的附属文件，安装后检查客户端能否发现该技能。

该技能引用了附属文件，请从来源获取完整目录；仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理，确认其中的目标目录与客户端匹配。

把 Agent Skill「telegram」安装到我的项目：SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-d6a72d498b8ce442-Telegram.html
请存为 .cursor/skills/telegram/SKILL.md 或 .claude/skills/telegram/SKILL.md，frontmatter 的 name 与 description 保持原样，不要改写。
该技能还带 scripts/、references/、assets/ 等文件，请从 https://clawhub.ai/skills/telegram 取完整目录，不要只建一个 SKILL.md。

当前没有明确的 GitHub 技能包地址，请按来源页面的安装器说明操作。

ClawHub ↗

SKILL.md 原文可复制，不会改动源文件

---
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.

阅读排版

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.

Telegram