tg-bot-ops skillB
tg-bot-ops is agent-read markdown (skill) from serejaris/personal-corp-os: 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 AP.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Telegram Bot Ops Use this skill when the real question is whether a Telegram bot is receiving updates, processing them in the intended runtime, and sending visible responses to the right chat, user, or forum topic. ## Public Safety - Default to read-only diagnostics. - Do not print tokens, `.env` values, connection strings, raw logs, private DMs, payment payloads, session files, or full user records. - Use placeholders in notes and examples: `<TELEGRAM_BOT_TOKEN>`, `<TELEGRAM_USER_ID>`, `<CHAT_ID>`, `<TOPIC_ID>`, `<WEBHOOK_URL>`. - Do not send Telegram messages, restart production services, change webhooks, edit BotFather settings, or deploy until the user has authorized that exact action. - If any real secret appears in the repo, logs, or prompt, stop and tell the user it must be rotated before public release. ## Intake If the repo or runtime is unclear, identify: - bot repo and language/runtime; - deployment target: local, Docker, VPS/systemd, Railway, Render, Fly, Vercel, or other; - update mode: webhook, polling, or unknown; - env source for `TELEGRAM_BOT_TOKEN`; - expected symptom, chat surface, and timestamp; - whether production restart/deploy is allowed. …
Read the whole file at its exact version.
How to install
mdr add serejaris/personal-corp-os/tg-bot-ops@git:20260601.4aa6ad0mdr add serejaris/personal-corp-os/tg-bot-ops@sha256:e47447c50b646608Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_a2cylr6uci73ijzo)
1 badge views in 30 days
Versions
Audit of the latest version
- fail: No instruction to read or print local credentials (matched: print tokens, `.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6415 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
serejaris/personal-corp-os · 228 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a2cylr6uci73ijzo GET https://markdownregistry.com/api/v1/resolve?ref=serejaris/personal-corp-os/tg-bot-ops GET https://markdownregistry.com/api/v1/blob/e47447c50b6466083c3f3b01eb33401a1a0341652f9f071dab40ba3425154c78
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.