tg-bot-ops

Diagnose Telegram bot webhook, polling, and gateway routing issues.

215|26|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/serejaris/personal-corp-skills --skill tg-bot-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tg-bot-ops
Source: https://github.com/serejaris/personal-corp-skills/tree/main/skills/tg-bot-ops
Command: npx skills add https://github.com/serejaris/personal-corp-skills --skill tg-bot-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use this skill when operating, debugging, deploying, or monitoring a Telegram bot or Telegram-to-agent gateway. Triggers on "telegram bot down", "bot not responding", "debug bot", "check webhook", "polling vs webhook", "restart bot", "deploy bot", "bot logs", "agent gateway", "Telegram Bot API error", "send test message", "бот не отвечает", "проверь бота", "логи бота", "перезапусти бота". Covers health checks, logs, webhook/polling diagnostics, environment validation, safe restart/deploy checklists, Bot API smoke tests, forum topic delivery, privacy mode, gateway routing, and incident notes.

Core Features & Use Cases

  • Diagnostic flow covers repo/runtime inspection, environment variable checks, webhook/polling verification, and agent-turn traceability.
  • Supports Telegram-To-Agent Gateways references and safe restart procedures.
  • Use Case: When bot is unresponsive or gateway routing fails, provide a structured incident report and remediation steps.

Quick Start

Provide the Telegram bot environment with TELEGRAM_BOT_TOKEN, validate webhook or polling, and run a smoke test to confirm the bot responds.

Frequently Asked Questions about tg-bot-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is my Telegram bot not responding to messages?

A Telegram bot not responding typically indicates webhook routing failures, polling conflicts, or missing environment variables. Diagnose by inspecting bot logs, validating the TELEGRAM_BOT_TOKEN, and verifying webhook or polling configurations to identify the exact delivery breakdown.

How do I check if my Telegram webhook is working?

Check Telegram webhook status by running a Bot API smoke test and reviewing gateway routing logs. Verify environment variables, confirm the endpoint is reachable, and inspect incident notes to ensure updates are properly delivered and not failing due to token or routing misconfigurations.

Should I use polling or webhooks for my Telegram bot?

Polling and webhooks serve different deployment needs for Telegram bots. Webhooks require a publicly accessible endpoint for real-time updates, while polling actively fetches messages. Diagnose both configurations to determine which method aligns with your local or cloud runtime environment.

How do I safely restart a Telegram bot after a crash?

Safely restart a crashed Telegram bot by following a structured checklist that masks tokens and avoids exposing secrets. Validate environment variables, inspect runtime logs, and execute a Bot API smoke test to confirm the bot responds before resuming full gateway operations.

How do I debug a Telegram-to-agent gateway routing failure?

Debug Telegram-to-agent gateway routing failures by inspecting agent-turn traceability logs and verifying webhook delivery. Run environment validation checks and structured diagnostics to trace where the routing breaks down between the Telegram Bot API and your agent runtime.

Can I test my Telegram bot locally without deploying to a server?

Test Telegram bots locally using polling mode instead of webhooks to receive updates without a public endpoint. Validate environment variables like TELEGRAM_BOT_TOKEN locally and run Bot API smoke tests to confirm bot responses before cloud deployment.