Tg Bot Ops

What it does

When your agent uses it

• Monitoring a Telegram bot
• Telegram-to-agent gateway
• Telegram bot down
• Bot not responding

Example prompts

• “telegram bot down”
• “bot not responding”
• “debug bot”
• “/tg-bot-ops”

Requirements

• Python 3
• Docker
• A credential in TELEGRAM_BOT_TOKEN

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

1. 1Repo and runtime — inspect entrypoints, process manager, deploy files, and
2. 2Environment — verify required env var names exist without printing values.
3. 3Update intake — classify runtime: HTTP Bot API webhook, HTTP Bot API
4. 4Bot API identity — for Bot API-token runtimes, run getMe using a masked token path.
5. 5Webhook/polling mode — for Bot API-token runtimes, run getWebhookInfo
6. 6Single update owner — resolve 409 Conflict by reading the error text
7. 7Telegram delivery — use a fresh nonce for Bot API or Telethon/user-session
8. 8Handler/runtime — prove the runtime received and processed the update.
9. 9Outbound response — prove the bot sent to the expected chat/topic.
10. 10Incident note — report symptom, evidence, root cause, fix, and residual risk.

What it can do on your machine

Read from SKILL.md and the folder at commit 95e36c3. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • api.telegram.org

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • TELEGRAM_BOT_TOKEN

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tg Bot Ops loads about 1.6k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 150 tokens; SKILL.md has 716 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~150

When it runs · the whole SKILL.md, loaded when a task matches

~1.6k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:15

  - Do not print tokens, `.env` values, connection strings, raw logs, private DMs,

• NoteMentions a .env fileSKILL.md:132

  - Printing raw bot tokens, `.env`, logs, user messages, payment payloads, or DB rows.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from serejaris/personal-corp-os at commit 95e36c3, republished under its MIT licence (© serejaris). 716 words, ~1,585 tokens.

name

tg-bot-ops

description

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

import json, os, urllib.request

token = os.environ["TELEGRAM_BOT_TOKEN"]
for method in ("getMe", "getWebhookInfo"):
    with urllib.request.urlopen(f"https://api.telegram.org/bot{token}/{method}") as response:
        data = json.load(response)
    print(method, {"ok": data.get("ok"), "result_keys": sorted((data.get("result") or {}).keys())})

getWebhookInfo: webhook_url=<set|empty>, pending_update_count=<n>, last_error=<redacted>

© serejaris, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references, assets) in skills/tg-bot-ops of serejaris/personal-corp-os.

• SKILL.md
• README.md
• README.ru.md
• assets/illustration.png
• references/hermes-gateway.md

Open the folder on GitHubat commit 95e36c3