Agent skill

Telegram Daemon Monitor

by k1p1l0 in k1p1l0/claude-telegram-supercharged

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

Apache-2.0Auto-check passedDevOps & Cloud

Install Telegram Daemon Monitor

skills CLI

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

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

GitHub CLI

$ gh skill install k1p1l0/claude-telegram-supercharged monitor --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/monitor .claude/skills/monitor && 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/

Paste into Claude Code

Install the "monitor" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/monitor into .claude/skills/monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitor", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/monitor

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add k1p1l0/claude-telegram-supercharged --skill monitor -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install k1p1l0/claude-telegram-supercharged monitor --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "monitor" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/monitor into .agents/skills/monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitor", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add k1p1l0/claude-telegram-supercharged --skill monitor -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install k1p1l0/claude-telegram-supercharged monitor --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "monitor" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/monitor into .cursor/skills/monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitor", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/k1p1l0/claude-telegram-supercharged.git --path skills/monitor

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add k1p1l0/claude-telegram-supercharged --skill monitor -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install k1p1l0/claude-telegram-supercharged monitor --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "monitor" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/monitor into .gemini/skills/monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitor", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install k1p1l0/claude-telegram-supercharged monitor

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add k1p1l0/claude-telegram-supercharged --skill monitor -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "monitor" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/monitor into .github/skills/monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitor", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add k1p1l0/claude-telegram-supercharged --skill monitor -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install k1p1l0/claude-telegram-supercharged monitor --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "monitor" agent skill from https://github.com/k1p1l0/claude-telegram-supercharged/tree/master/skills/monitor into .opencode/skills/monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monitor", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: monitor
GitHub stars: 131
Token cost: ~746 tokens
SKILL.md length: 197 words
Files: 1
Skills in repo: 5
Repo updated: Sep 26, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

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

Works in 6 steps: Process status → Launchd status → Recent supervisor logs → …
Checking whether the Telegram bot daemon is running
SKILL.md covers What to check, Output format and Arguments
Calls bun and claude; reaches claude.ai

What it does

This is the status check for the Telegram daemon that keeps Claude running from a Telegram bot. It lists the supervisor, expect wrapper, Claude bot, MCP server and caffeinate processes with their PIDs and uptime, reports whether the launchd job is loaded, shows the latest supervisor log lines for crashes, restarts or errors, and scans stdout for MCP server problems.

It also pulls the remote control URL for the session so you can watch the daemon live in a browser, and reads the lock file to show whether the PID in it is still alive. Results appear as a status table. Arguments narrow the output: logs shows the last 30 stderr lines, stdout shows the last 30 lines of Claude's output, url shows only the remote control URL, and restart prints the restart command for you to run rather than running it.

When your agent uses it

Checking whether the Telegram bot daemon is running
Reading recent supervisor logs after the bot stops responding
Finding the remote control URL for the running session
Diagnosing why the MCP server failed to start

Example prompts

“Is the daemon running? Run the Telegram monitor.”
“Show me the last 30 lines of the supervisor logs.”
“Give me just the remote control URL for the bot.”

Requirements

The Telegram daemon plugin for Claude Code, already installed
launchctl, for the launchd status check
Pre-approved tools (allowed-tools): Bash(ps *), Bash(tail *), Bash(cat *), Bash(grep *), Bash(launchctl *), Bash(strings *), Bash(head *), Bash(wc *), Read

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Process status
Launchd status
Recent supervisor logs
MCP server health
Remote control URL
Lock file

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(ps *)
- Bash(tail *)
- Bash(cat *)
- Bash(grep *)
- Bash(launchctl *)
- Bash(strings *)
- Bash(head *)
- Bash(wc *)
- Read
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- bun
- claude
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- claude.ai
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 Monitor loads about 746 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 197 words of instructions outside code blocks.

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

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). 197 words, ~746 tokens.

Download SKILL.mdSave it as .claude/skills/monitor/SKILL.md (or your agent's skills folder).

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".
allowed-tools: Bash(ps *), Bash(tail *), Bash(cat *), Bash(grep *), Bash(launchctl *), Bash(strings *), Bash(head *), Bash(wc *), Read
user-invocable: true

/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

Files

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

Open the folder on GitHubat commit 688e8fc

Compare with similar skills

Telegram Daemon Monitor 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 Monitor compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Telegram Daemon Monitor this skillk1p1l0/claude-telegram-supercharged	131	—	~746	Automated safety check: Pass	Apache-2.0	12 days ago
Greptimedb Perses DashboardGreptimeTeam/dashboard	111	—	~3.9k	Automated safety check: Pass	Apache-2.0	8 days ago
AWS Cost Operationszxkane/aws-skills	367	1 repos	~2.4k	Automated safety check: Pass	MIT	3 mo ago
AWS Cost Operationssickn33/agentic-awesome-skills	47k	1 repos	~2.4k	Automated safety check: Pass	MIT	yesterday
Assistant MCPgrafana/skills	279	—	~1.2k	Automated safety check: Pass	Apache-2.0	2 days ago
AWS Cost OperationsMicrock/ordinary-claude-skills	403	1 repos	~2.5k	Automated safety check: Pass	Custom licence	1 mo ago

Similar skills

Greptimedb Perses Dashboard
GreptimeTeam/dashboard
Generate Perses dashboards or single panels for GreptimeDB. An agent skill from GreptimeTeam/dashboard.
111 GitHub stars~3.9k tokensUpdated 8 days ago
DevOps & CloudAuto-check passed
AWS Cost Operations
zxkane/aws-skills
AWS cost optimization, monitoring, and operational excellence expert.
367 GitHub starsUsed in 1 repo~2.4k tokens
DevOps & CloudAuto-check passed
AWS Cost Operations
sickn33/agentic-awesome-skills
AWS cost optimization, monitoring, and operational excellence expert.
47k GitHub starsUsed in 1 repo~2.4k tokens
DevOps & CloudAuto-check passed
Assistant MCP
grafana/skills
Official
Connect AI coding agents (Claude Code, Cursor, VS Code, OpenAI Codex) to Grafana Cloud via the mcp-grafana Model Context Protocol server.
279 GitHub stars~1.2k tokensUpdated 2 days ago
DevOps & CloudAuto-check passed
AWS Cost Operations
Microck/ordinary-claude-skills
This skill provides AWS cost optimization, monitoring, and operational best practices with integrated MCP servers for billing analysis, cost estimation, observability, and security assessment.
403 GitHub starsUsed in 1 repo~2.5k tokens
DevOps & CloudAuto-check passed
Myagents CLI
hAcKlyc/MyAgents
你正在 MyAgents 这款 AI 产品里运行——MyAgents 自带一套"产品能力"（定时任务、任务中心、记录收集、MCP 工具接入、模型 Provider、IM Bot 渠道、社区插件、Skills 安装、协作空间、Agent 网络与 Session 协作、Generative UI Widget、Goal 目标模式等），通过内置 myagents CLI 操作。
918 GitHub stars~8.8k tokensUpdated yesterday
Productivity & AutomationAuto-check: warnings

Questions about Telegram Daemon Monitor

What does Telegram Daemon Monitor do?

Checks whether the Telegram daemon is alive, shows recent logs, finds the remote control URL and diagnoses MCP server problems. This is the status check for the Telegram daemon that keeps Claude running from a Telegram bot. It lists the supervisor, expect wrapper, Claude bot, MCP server and caffeinate processes with their PIDs and uptime, reports whether the launchd job is loaded, shows the latest supervisor log lines for crashes, restarts or errors, and scans stdout for MCP server problems.

When should I use Telegram Daemon Monitor?

Telegram Daemon Monitor fits situations like: checking whether the Telegram bot daemon is running; reading recent supervisor logs after the bot stops responding; finding the remote control URL for the running session; diagnosing why the MCP server failed to start.

How do I install Telegram Daemon Monitor in Claude Code?

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

How do I install Telegram Daemon Monitor in Codex?

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

Can I use Telegram Daemon Monitor 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 monitor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monitor, .gemini/skills/monitor, .github/skills/monitor and .opencode/skills/monitor in your project.

What does Telegram Daemon Monitor need to run?

Going by SKILL.md and its folder, Telegram Daemon Monitor needs the command-line tools its instructions call (bun and claude). Our summary lists: The Telegram daemon plugin for Claude Code, already installed; launchctl, for the launchd status check. Its frontmatter pre-approves these tools: Bash(ps *), Bash(tail *), Bash(cat *), Bash(grep *), Bash(launchctl *), Bash(strings *), Bash(head *), Bash(wc *), Read.

Does Telegram Daemon Monitor access the network?

SKILL.md names 1 domain. In commands or code: claude.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Telegram Daemon Monitor 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 Monitor use?

Telegram Daemon Monitor 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 Monitor use?

About 746 tokens (SKILL.md is roughly 3k 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 Monitor?

Skills that share tags, products or a category with Telegram Daemon Monitor: Greptimedb Perses Dashboard (GreptimeTeam/dashboard, 111 stars), AWS Cost Operations (zxkane/aws-skills, 367 stars), AWS Cost Operations (sickn33/agentic-awesome-skills, 47k stars) and Assistant MCP (grafana/skills, 279 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Telegram Daemon Monitor?

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.

Install Telegram Daemon Monitor

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

/telegram:monitor — Telegram Daemon Monitor

What to check

1. Process status

2. Launchd status

3. Recent supervisor logs

4. MCP server health

5. Remote control URL

6. Lock file

Output format

Arguments

Files

Compare with similar skills

Similar skills

More from k1p1l0/claude-telegram-supercharged

Related

Questions about Telegram Daemon Monitor