Agent skill

Telegram Daemon Manager

by k1p1l0 in k1p1l0/claude-telegram-supercharged

Starts, stops, restarts and checks the launchd-managed Telegram bot daemon for Claude Code, and tails its supervisor logs and remote control URL.

Apache-2.0Auto-check passedProductivity & Automation

Install Telegram Daemon Manager

skills CLI
$ npx skills add k1p1l0/claude-telegram-supercharged --skill daemon -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install k1p1l0/claude-telegram-supercharged daemon --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/k1p1l0/claude-telegram-supercharged.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/daemon .claude/skills/daemon && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
daemon
GitHub stars
131
Token cost
~682 tokens
SKILL.md length
236 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Starts, stops, restarts and checks the launchd-managed Telegram bot daemon for Claude Code, and tails its supervisor logs and remote control URL.

  • Works in 5 steps: Process status (supervisor, expect,… → Launchd loaded/not → Remote control URL → …
  • Starting or stopping the Telegram bot daemon on your Mac
  • SKILL.md covers Arguments — dispatch on first… and Important notes
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This slash command manages the background daemon behind the Telegram bot setup, which runs under launchd with a supervisor and Claude. It dispatches on the first word. Start loads the launch agent plist, waits a few seconds and checks status. Stop unloads it, waits and confirms no processes remain, reporting any orphans. Restart does both and then runs a full status check. With no argument it checks whether the daemon is running and either shows status or asks whether to start it.

Status covers the supervisor, expect, claude, MCP server and caffeinate processes, whether launchd has it loaded, the remote control URL, the lock file and the last five log lines. Logs and stdout show the last 30 lines of the supervisor's stderr and the daemon's Claude output, and url prints the session link. It notes that launchctl may return an input/output error when the service is already in the requested state, and that the URL should be shown after every start or restart.

When your agent uses it

  • Starting or stopping the Telegram bot daemon on your Mac
  • Checking whether the Telegram bot is still running
  • Reading the supervisor logs after the bot stops responding
  • Finding the remote control URL for the running daemon

Example prompts

  • “Is the Telegram bot running right now?”
  • “Restart the daemon and show me the remote control URL once it is back.”
  • “Show the last supervisor error log lines for the Telegram daemon.”
  • “Stop the bot and make sure no orphan processes are left behind.”

Requirements

  • macOS with launchd
  • The Telegram daemon launch agent plist installed in the user's LaunchAgents folder
  • Pre-approved tools (allowed-tools): Bash(launchctl *), Bash(ps *), Bash(tail *), Bash(cat *), Bash(grep *), Bash(strings *), Bash(kill *), Read

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 688e8fc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(launchctl *)
    • Bash(ps *)
    • Bash(tail *)
    • Bash(cat *)
    • Bash(grep *)
    • Bash(strings *)
    • Bash(kill *)
    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Telegram Daemon Manager loads about 682 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 236 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~682

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from k1p1l0/claude-telegram-supercharged at commit 688e8fc, republished under its Apache-2.0 licence (© k1p1l0). 236 words, ~682 tokens.

Download SKILL.mdSave it as .claude/skills/daemon/SKILL.md (or your agent's skills folder).
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".
allowed-tools
Bash(launchctl *), Bash(ps *), Bash(tail *), Bash(cat *), Bash(grep *), Bash(strings *), Bash(kill *), Read
user-invocable
true

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

© k1p1l0, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/daemon of k1p1l0/claude-telegram-supercharged.

Open the folder on GitHubat commit 688e8fc

Compare with similar skills

Telegram Daemon Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Telegram Daemon Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Telegram Daemon Manager this skillk1p1l0/claude-telegram-supercharged131—~682Automated safety check: PassApache-2.0
Relay For TelegramLeoYeAI/openclaw-master-skills2.2k—~6kAutomated safety check: PassMIT
LangBot EBA Adapter Developmentlangbot-app/LangBot18k—~4kAutomated safety check: PassApache-2.0
Agenticmailagenticmail/agenticmail235—~3.9kAutomated safety check: PassMIT
Claude To Imop7418/Claude-to-IM-skill2.9k—~3.4kAutomated safety check: NotesMIT
Tlivey49/tlive2141 repos~1.7kAutomated safety check: NotesMIT

Similar skills

  • Relay For Telegram

    LeoYeAI/openclaw-master-skills

    The best way to access Telegram message history. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~6k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed
  • Guides building, migrating and testing LangBot messaging-platform adapters for the Event-Based Agents layout, with unified event and message conversion.

    18k GitHub stars~4k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Agenticmail

    agenticmail/agenticmail

    🎀 AgenticMail — Full email, SMS, phone call-control, Telegram, media, memory, storage & multi-agent coordination for AI agents.

    235 GitHub stars~3.9k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • Claude To Im

    op7418/Claude-to-IM-skill

    Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone.

    2.9k GitHub stars~3.4k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check: notes
  • Tlive

    y49/tlive

    tlive — remote approvals (Telegram/Feishu/web), live web terminal, and session monitoring for Claude Code / Codex.

    214 GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check: notes
  • Drives the traul CLI to sync, search and monitor messages from Slack, Telegram, Discord, Linear, Gmail, WhatsApp, Claude Code sessions and Markdown files.

    113 GitHub stars~3.9k tokensUpdated 5 mo ago
    Productivity & AutomationAuto-check: notes

More from k1p1l0/claude-telegram-supercharged

  • Google Calendar via Telegram

    k1p1l0/claude-telegram-supercharged

    Manages Google Calendar from a Telegram chat: lists the schedule, creates and updates events, finds free time and sends daily briefings and reminders.

    131 GitHub stars~791 tokensUpdated 12 days ago
    Auto-check passed
  • Telegram Context Transfer

    k1p1l0/claude-telegram-supercharged

    Hands the current Claude Code session's context to a Telegram bot session by writing a short summary to the bot's memory file and sending it as a Telegram message.

    131 GitHub stars~764 tokensUpdated 12 days ago
    Auto-check: notes
  • Telegram Daemon Monitor

    k1p1l0/claude-telegram-supercharged

    Checks whether the Telegram daemon is alive, shows recent logs, finds the remote control URL and diagnoses MCP server problems.

    131 GitHub stars~746 tokensUpdated 12 days ago
    Auto-check passed
  • Telegram Plugin Updater

    k1p1l0/claude-telegram-supercharged

    Updates the enhanced Telegram plugin for Claude Code from its GitHub repository: compares file hashes, shows recent commits, asks first, then runs the installer.

    131 GitHub stars~764 tokensUpdated 12 days ago
    Auto-check passed

Questions about Telegram Daemon Manager

What does Telegram Daemon Manager do?

Starts, stops, restarts and checks the launchd-managed Telegram bot daemon for Claude Code, and tails its supervisor logs and remote control URL. This slash command manages the background daemon behind the Telegram bot setup, which runs under launchd with a supervisor and Claude. It dispatches on the first word.

When should I use Telegram Daemon Manager?

Telegram Daemon Manager fits situations like: starting or stopping the Telegram bot daemon on your Mac; checking whether the Telegram bot is still running; reading the supervisor logs after the bot stops responding; finding the remote control URL for the running daemon.

How do I install Telegram Daemon Manager in Claude Code?

Run `npx skills add k1p1l0/claude-telegram-supercharged --skill daemon -a claude-code`. Or copy the skill folder (skills/daemon in k1p1l0/claude-telegram-supercharged) into .claude/skills/daemon in your project. Claude Code loads it when a task matches its description.

How do I install Telegram Daemon Manager in Codex?

Run `npx skills add k1p1l0/claude-telegram-supercharged --skill daemon -a codex`. Or copy the skill folder (skills/daemon in k1p1l0/claude-telegram-supercharged) into .agents/skills/daemon in your project. Codex loads it when a task matches its description.

Can I use Telegram Daemon Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add k1p1l0/claude-telegram-supercharged --skill daemon -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/daemon, .gemini/skills/daemon, .github/skills/daemon and .opencode/skills/daemon in your project.

What does Telegram Daemon Manager need to run?

SKILL.md names no scripts, command-line tools or credentials: Telegram Daemon Manager is instructions for the agent only. Our summary lists: macOS with launchd; The Telegram daemon launch agent plist installed in the user's LaunchAgents folder. Its frontmatter pre-approves these tools: Bash(launchctl *), Bash(ps *), Bash(tail *), Bash(cat *), Bash(grep *), Bash(strings *), Bash(kill *), Read.

Does Telegram Daemon Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Telegram Daemon Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Telegram Daemon Manager use?

Telegram Daemon Manager is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Telegram Daemon Manager use?

About 682 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Telegram Daemon Manager?

Skills that share tags, products or a category with Telegram Daemon Manager: Relay For Telegram (LeoYeAI/openclaw-master-skills, 2.2k stars), LangBot EBA Adapter Development (langbot-app/LangBot, 18k stars), Agenticmail (agenticmail/agenticmail, 235 stars) and Claude To Im (op7418/Claude-to-IM-skill, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Telegram Daemon Manager?

k1p1l0 (a GitHub user) maintains it in k1p1l0/claude-telegram-supercharged, which has 131 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 26, 2026.

Source: k1p1l0/claude-telegram-supercharged on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.