Telegram Bot API Skill

Use this skill to run Telegram Bot API operations through uxc + OpenAPI.

Reuse the uxc skill for shared execution, auth, and error-handling guidance.

Prerequisites

• - uxc is installed and available in PATH.
• Network access to https://api.telegram.org.
• Access to the curated OpenAPI schema URL:

• - A Telegram bot token from BotFather.

Scope

This skill covers a lean bot core surface:

• - bot identity and chat lookup
• text sends
• media sends by file_id, HTTP URL, or local multipart upload
• polling via INLINECODE7
• webhook setup/status/delete operations

This skill does not cover:

• - multipart media groups with attach:// file arrays
• generic webhook ingestion/runtime hosting
• the full Telegram Bot API surface

Authentication

Telegram Bot API requires the bot token in the request path: https://api.telegram.org/bot<TOKEN>/METHOD_NAME.

Configure the credential with a request path prefix template:

CODEBLOCK0

Validate the local mapping when auth looks wrong:

CODEBLOCK1

Core Workflow

1. 1. Use the fixed link command by default:

1. 2. Inspect operation schema first:

1. 3. Prefer read/setup validation before writes:

1. 4. Execute operations with key/value or positional JSON:

Runtime Validation

The following Telegram polling flow has been validated against the real Bot API through uxc:

• - INLINECODE26
• INLINECODE27
• daemon-backed uxc subscribe --mode poll on INLINECODE29
• item-derived offset progression from INLINECODE30
• dedupe/checkpoint behavior for repeated polls

Observed runtime behavior:

• - data events are emitted for real Telegram updates
• INLINECODE32 events record fetched/emitted/skipped counts
• INLINECODE33 events are emitted after new updates are seen
• repeated polls skip already-consumed updates after checkpoint advancement

Operation Groups

Read / Lookup

• - INLINECODE34
• INLINECODE35
• INLINECODE36
• INLINECODE37

Messaging

• - INLINECODE38
• INLINECODE39
• INLINECODE40
• INLINECODE41

Update Delivery

• - INLINECODE42
• INLINECODE43
• INLINECODE44

Guardrails

• - Keep automation on the JSON output envelope; do not use --text.
• Parse stable fields first: ok, kind, protocol, data, error.
• INLINECODE51 and webhook delivery are mutually exclusive:

• - Telegram allows only one active getUpdates consumer per bot token:

• - For daemon-backed polling subscribe, prefer item-derived offset progression:

• - uxc auth binding match should be checked against a concrete Telegram method URL such as https://api.telegram.org/getMe, because auth is applied through a path-prefix template that expands to /bot<TOKEN>/....
• INLINECODE69, sendDocument, and sendMediaGroup in this skill accept existing file_id values or HTTP URLs only; they do not upload new local files.
• INLINECODE73 and sendDocument also support multipart/form-data local file uploads. File fields must be local path strings.
• INLINECODE76 still stays JSON-only in this skill because current multipart v1 does not model the media array plus attach:// file set cleanly.
• INLINECODE79 supports multipart certificate upload for self-signed certs through the certificate file field.
• Treat post:/sendMessage, all send* operations, and webhook-changing operations as write/high-risk actions; require explicit user confirmation before execution.
• INLINECODE83 is equivalent to uxc https://api.telegram.org --schema-url <telegram_openapi_schema> <operation> ....

References

• - Usage patterns: INLINECODE85
• Curated OpenAPI schema: INLINECODE86
• Telegram Bot API docs: https://core.telegram.org/bots/api
• Local Bot API server: https://github.com/tdlib/telegram-bot-api