agentleFS
Sign inStart free
k1p1l0k1p1l0/claude-telegram-supercharged/skills/daemon/SKILL.md

daemon

Skill144 starsChanged 8 months agoApache-2.0View on GitHub

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

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. SethGammon/Citadel★ 927same name
    2. mayankjain1815-commits/CITADEL★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Start the daemon via launchd:

    line 24
  2. Distinctive:

    If it fails with "already loaded", report that the daemon is already running.

    line 30
  3. Distinctive:

    After loading, wait 5 seconds, then run the status check to confirm it started.

    line 31
  4. Distinctive:

    Wait 3 seconds, verify all processes are gone:

    line 41
  5. Distinctive:

    Wait 10 seconds, then run full status check.

    line 59
  6. Distinctive:

    Run the full monitor check — same as /telegram:monitor:

    line 63
  7. Distinctive:

    Check if daemon is running.

    line 97
  8. Distinctive:

    After start/restart, always verify the daemon actually started by checking processes.

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  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:

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free