メニュー
Manage the Telegram Topics daemon — check status, stop it, or tail its log. Use when the user asks about the daemon process, wants to stop it, or wants to debug why messages aren't flowing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Set up the Telegram Topics channel — save the bot token, configure the supergroup chat ID, set topic names, or get the launch recipe for a secondary same-project instance. Use when the user pastes a bot token, asks to configure Telegram Topics, wants to check channel status, or needs to run a second Claude session in the same directory with its own topic.
Show the telegram-topics plugin help — list all commands and the typical setup flow. Use when the user asks what they can do with telegram-topics, wants a command list, or doesn't know where to start.
List registered projects and their Telegram topic mappings, or remove a topic (with a two-step confirmation). Use when the user wants to see which projects have topics, check topic IDs, or delete a topic.
Approve a Telegram Topics pairing code. Shorthand for /telegram-topics:access pair. Use when the user just got a pairing code from their bot and wants to authorize their account.
Manage Telegram Topics channel access — approve pairings, edit allowlists, set policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy.
| name | daemon |
| description | Manage the Telegram Topics daemon — check status, stop it, or tail its log. Use when the user asks about the daemon process, wants to stop it, or wants to debug why messages aren't flowing. |
| user-invocable | true |
| allowed-tools | ["Read","Bash(kill *)","Bash(ps *)","Bash(tail *)"] |
Arguments passed: $ARGUMENTS
status~/.claude/channels/telegram-topics/daemon.pid.--channels will auto-start it)."kill -0 <pid>.ps -p <pid> -o lstart=).ps -p <pid> -o args=). If the path contains
plugins/cache/<marketplace>/<plugin>/<version>, that version is what
the daemon is running.~/.claude/plugins/cache/ for the latest), the daemon is stale
and should be stopped so the next session can spawn the updated one.stopdaemon.pid.SIGTERM: kill <pid>.kill -0), send SIGKILL: kill -9 <pid>.restart--channels.
The shim also auto-detects stale daemons (from outdated plugin cache paths)
on connect and replaces them, so normally no manual action is needed after
/plugin update."logTail the daemon log at ~/.claude/channels/telegram-topics/daemon.log.
Show the last ~50 lines. Useful for debugging when messages don't route.
Common lines to look for:
inbound chat=... thread=... sender=... — a message arrived from Telegramgate result for <id> = deliver — sender is allowedgate result for <id> = drop — sender is blocked (not in allowFrom)routing topic=N → shim for /path — routed successfully to a shimrouting topic=N → NO SHIM — no Claude Code session connected for this topicdrop — chat X != configured Y — message is in a different chat than the configured onedrop — no message_thread_id — message was not in a Forum Topic409 Conflict — another process is polling with the same bot token