daemon
/daemon
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".
- 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
- 0
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
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".
Triggers from the description
Original author description
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".
How it works
- Arguments — dispatch on first word
- Important notes
SKILL.md preview
--- name: daemon description: 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". user-invocable: true allowed-tools: - Bash(launchctl *) - Bash(ps *) - Bash(tail *) - Bash(cat *) - Bash(grep *) - Bash(strings *) - Bash(kill *) - Read --- # /telegram:daemon — Telegram Daemon Lifecycle Manager Full lifecycle management for the Telegram bot daemon (launchd + supervisor + Claude). ## Arguments — dispatch on first word ### `start` (default if no args and daemon is not running) Start the daemon via launchd: ```bash launchctl load ~/Library/LaunchAgents/com.user.claude-telegram.plist 2>&1 ``` If it fails with "already loaded", report that the daemon is already running. After loading, wait 5 seconds, then run the status check to confirm it started. ### `stop` Stop the daemon: ```bash launchctl unload ~/Library/LaunchAgents/com.user.claude-telegram.plist 2>&1 ``` Wait 3 seconds, verify all processes are gone: ```bash ps aux | grep -E "channels.*telegram" | grep -v grep ``` Report success or if orphan processes remain. ### `restart` Unload then load: ```bash launchctl unload ~/Library/LaunchAgents/com.user.claude-telegram.plist 2>/dev/null sleep 2 launchctl load ~/Library/LaunchAgents/com.user.claude-telegram.plist ``` Wait 10 seconds, then run full status check. ### `status` (default if no args and daemon IS running) Run the full monitor check — same as /telegram:monitor: 1. Process status (supervisor, expect, claude, MCP server, caffeinate) 2. Launchd loaded/not 3. Remote control URL 4. Lock file 5. Last 5 log lines ### `logs` Tail the last 30 lines of supervisor stderr: ```bash tail -30 ~/.claude/channels/telegram/data/supervisor-stderr.log ``` ### `stdout` Tail the last 30 lines of daemon's Claude output: ```bash tail -30 ~/.claude/channels/telegram/data/supervisor-stdout.log ``` ### `url` Just show the remote control URL: ```bash cat ~/.claude/channels/telegram/data/supervisor-stdout.log | strings | grep "session_" | tail -1 ``` ### No args Check if daemon is running. If running → show status. If not running → ask if user wants to start it. ## Important notes - The `launchctl load/unload` commands may fail with "Input/output error" — this usually means the service is already in the requested state. Handle gracefully. - After start/restart, always verify the daemon actually started by checking processes. - The plist path is always: `~/Library/LaunchAgents/com.user.claude-telegram.plist` - Show the remote control URL after every start/restart so the user can monitor.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · k1p1l0/claude-telegram-supercharged | 100 | Apache-2.0 |
| danielmiessler/LifeOS | 95 | MIT |
Database snapshot: 13.11.2026 · package version 95a3e1778701 (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
- 100monitor
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". - 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… - 100daemon-ops
Operational commands for the AgentX daemon on the current host — restart, tail logs, hot-reload config, status, Claude-auth and overage-gate troubleshooting. Works on both macOS (launchd) and Linux (systemd). Intended for the devops / main agent on the host. Other agents should not use this. - 90manage-local-services
Manage workflow daemon services - MCP, SLOP, Slack, Ollama, Scheduler. Start, stop, restart, status. Use when user says "start MCP", "restart slack daemon", "service status". - 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. - 95b2c-sandbox
Create and manage on-demand sandboxes (ODS) for B2C Commerce using the b2c CLI. Use this skill whenever the user needs to spin up a new development sandbox, list running sandboxes, start/stop/restart an instance, or manage sandbox lifecycle — even if they just say "I need a…