メニュー
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".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Transfer context from the current Claude Code terminal session to the Telegram bot session. Use when the user says "send this to telegram", "transfer context", "telegram:context", "teleport to telegram", or wants the Telegram bot to continue work from this session.
Update the Telegram Supercharged plugin to the latest version from GitHub. Use when the statusline shows "⬆ Supercharged", or when the user says "update telegram plugin", "update supercharged", or "telegram:update".
Google Calendar integration — check schedule, create events, daily briefings, proactive reminders. Triggers on "what's on my calendar", "add to calendar", "schedule a meeting", "when am I free", "daily briefing", or any calendar-related request.
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".
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks "how do I set this up" or "who can reach me," or wants to check channel status.
| 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". |
| user-invocable | true |
| allowed-tools | ["Bash(ps *)","Bash(tail *)","Bash(cat *)","Bash(grep *)","Bash(launchctl *)","Bash(strings *)","Bash(head *)","Bash(wc *)","Read"] |
Shows the health and status of the Telegram daemon at a glance.
Run these checks and present a clean summary:
ps aux | grep -E "telegram-supervisor|channels.*telegram|expect.*daemon|caffeinate.*supervisor|bun server.ts" | grep -v grep
Report:
If no processes found, report "Daemon is NOT running."
launchctl list | grep claude-telegram
Report loaded/not loaded.
tail -10 ~/.claude/channels/telegram/data/supervisor-stderr.log
Show the last few log entries — look for crashes, restarts, orphan cleanup, or errors.
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.
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.
cat ~/.claude/channels/telegram/data/telegram.lock 2>/dev/null
Show the PID in the lock file and whether that process is still alive.
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]
logs — show last 30 lines of supervisor stderrstdout — show last 30 lines of stdout (Claude's output)restart — show the restart command for the user to runurl — just show the remote control URL