monitor
/monitor
Monitor the Telegram daemon — check if it's alive, view recent logs, find the remote control URL, and diagnose MCP server issues. Use when the user asks "is the daemon running", "check the bot", "show daemon logs", "monitor telegram", or "what's happening with the bot".
- Author
- k1p1l0 ↗
- Repository
- claude-telegram-supercharged ↗
- Licence
- Apache-2.0
- Last repository change
- 19.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Monitor the Telegram daemon — check if it's alive, view recent logs, find the remote control URL, and diagnose MCP server issues. Use when the user asks "is the daemon running", "check the bot", "show daemon logs", "monitor telegram", or "what's happening with the bot".
Triggers from the description
Original author description
Monitor the Telegram daemon — check if it's alive, view recent logs, find the remote control URL, and diagnose MCP server issues. Use when the user asks "is the daemon running", "check the bot", "show daemon logs", "monitor telegram", or "what's happening with the bot".
How it works
- What to check
- Output format
- Arguments
SKILL.md preview
--- name: monitor description: Monitor the Telegram daemon — check if it's alive, view recent logs, find the remote control URL, and diagnose MCP server issues. Use when the user asks "is the daemon running", "check the bot", "show daemon logs", "monitor telegram", or "what's happening with the bot". user-invocable: true allowed-tools: - Bash(ps *) - Bash(tail *) - Bash(cat *) - Bash(grep *) - Bash(launchctl *) - Bash(strings *) - Bash(head *) - Bash(wc *) - Read --- # /telegram:monitor — Telegram Daemon Monitor Shows the health and status of the Telegram daemon at a glance. ## What to check Run these checks and present a clean summary: ### 1. Process status ```bash ps aux | grep -E "telegram-supervisor|channels.*telegram|expect.*daemon|caffeinate.*supervisor|bun server.ts" | grep -v grep ``` Report: - **Supervisor** (bun telegram-supervisor.ts) — PID, uptime - **Expect wrapper** — PID - **Claude bot** (claude --channels ...) — PID, TTY, CPU/memory - **MCP server** (bun server.ts) — PID (if missing, the Telegram plugin didn't start) - **Caffeinate** — running or not If no processes found, report "Daemon is NOT running." ### 2. Launchd status ```bash launchctl list | grep claude-telegram ``` Report loaded/not loaded. ### 3. Recent supervisor logs ```bash tail -10 ~/.claude/channels/telegram/data/supervisor-stderr.log ``` Show the last few log entries — look for crashes, restarts, orphan cleanup, or errors. ### 4. MCP server health ```bash cat ~/.claude/channels/telegram/data/supervisor-stdout.log | strings | grep -i "MCP server" | tail -5 ``` Report any "MCP server needs a..." or "MCP servers fail" messages. ### 5. Remote control URL ```bash cat ~/.claude/channels/telegram/data/supervisor-stdout.log | strings | grep "session_" | tail -1 ``` Extract and show the `https://claude.ai/code/session_XXX` URL so the user can watch the daemon live in the browser. ### 6. Lock file ```bash cat ~/.claude/channels/telegram/data/telegram.lock 2>/dev/null ``` Show the PID in the lock file and whether that process is still alive. ## Output format Present as a clean status dashboard: ``` ## Telegram Daemon Status | Component | Status | PID | Details | |------------------|---------|-------|------------------| | Supervisor | ✅ alive | 12345 | uptime: 2h | | Claude bot | ✅ alive | 12346 | CPU: 0.5%, 300MB | | MCP server | ✅ alive | 12347 | | | Caffeinate | ✅ alive | 12348 | | | Launchd | ✅ loaded| | | **Remote control:** https://claude.ai/code/session_XXX **Lock file:** PID 12346 (alive) ### Recent logs [last 5 log entries] ``` ## Arguments - No args — full status check (default) - `logs` — show last 30 lines of supervisor stderr - `stdout` — show last 30 lines of stdout (Claude's output) - `restart` — show the restart command for the user to run - `url` — just show the remote control URL
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · k1p1l0/claude-telegram-supercharged | 100 | Apache-2.0 |
| x85446/claudecodetricks | 100 | MIT |
| nvidia/model-optimizer | 100 | MIT |
| tinyfish-io/tinyfish-web-agent-integrations | 100 | MIT |
| anthohunt/claude-code-skills | 100 | Apache-2.0 |
| spotify/ads-claude-plugin | 100 | Apache-2.0 |
| npow/claude-skills | 100 | Apache-2.0 |
| ialameh/sift-coder | 100 | MIT |
| yo-steven/skills-exploration-20260522 | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 58843ab1513c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100daemon
Manage the Telegram daemon lifecycle — start, stop, restart, check status, tail logs. Use when the user says "start the bot", "stop the daemon", "restart telegram", "daemon status", "show bot logs", or "is the bot running". - 100render-monitor
Monitor Render services in real-time. Check health, performance metrics, logs, and resource usage. Use when users want to check service status, view metrics, monitor performance, or verify deployments are healthy. - 100tg-bot-ops
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… - 95telegram-telethon
This skill should be used for comprehensive Telegram automation via Telethon API. Use for sending/receiving messages, monitoring chats, running a background daemon that triggers Codex sessions, managing channels/groups, and downloading media. Triggers on "telegram daemon",… - 100telegram-bot-manager
Manage and configure Telegram bots for OpenClaw. Use when setting up Telegram integrations, troubleshooting bot connectivity, configuring bot tokens, or managing Telegram channel/webhook settings. Handles bot registration, token validation, and network connectivity checks for api.telegram.org. - 100monitoring
Monitor Vercel deployments, debug production issues, check logs, and understand logging patterns. Use when investigating errors, checking deployment logs, debugging failures, or improving observability.