How do I install the Daemon skill?

Run npx skillmds@latest add k1p1l0/daemon in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Daemon safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Daemon?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Daemon free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Daemon?

k1p1l0 (@k1p1l0) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Daemon by k1p1l0 — Agent Skill

Name: Daemon
Author: k1p1l0

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

k1p1l0 2d6c508 2.5 KB Updated Sep 17, 2026

File contents

/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:

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:

launchctl unload ~/Library/LaunchAgents/com.user.claude-telegram.plist 2>&1

Wait 3 seconds, verify all processes are gone:

ps aux | grep -E "channels.*telegram" | grep -v grep

Report success or if orphan processes remain.

`restart`

Unload then load:

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:

Process status (supervisor, expect, claude, MCP server, caffeinate)
Launchd loaded/not
Remote control URL
Lock file
Last 5 log lines

`logs`

Tail the last 30 lines of supervisor stderr:

tail -30 ~/.claude/channels/telegram/data/supervisor-stderr.log

`stdout`

Tail the last 30 lines of daemon's Claude output:

tail -30 ~/.claude/channels/telegram/data/supervisor-stdout.log

`url`

Just show the remote control URL:

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.

---name: daemondescription: 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".---# /telegram:daemon — Telegram Daemon Lifecycle ManagerFull 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:```bashlaunchctl 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:```bashlaunchctl unload ~/Library/LaunchAgents/com.user.claude-telegram.plist 2>&1```Wait 3 seconds, verify all processes are gone:```bashps aux | grep -E "channels.*telegram" | grep -v grep```Report success or if orphan processes remain.### `restart`Unload then load:```bashlaunchctl unload ~/Library/LaunchAgents/com.user.claude-telegram.plist 2>/dev/nullsleep 2launchctl 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/not3. Remote control URL4. Lock file5. Last 5 log lines### `logs`Tail the last 30 lines of supervisor stderr:```bashtail -30 ~/.claude/channels/telegram/data/supervisor-stderr.log```### `stdout`Tail the last 30 lines of daemon's Claude output:```bashtail -30 ~/.claude/channels/telegram/data/supervisor-stdout.log```### `url`Just show the remote control URL:```bashcat ~/.claude/channels/telegram/data/supervisor-stdout.log | strings | grep "session_" | tail -1```### No argsCheck 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.

Frequently asked questions