メニュー
OpenClaw-specific checklist for Telegram live verification. Use when validating Telegram behavior against a live bot, especially thread/topic behavior, runtime ownership, userbot CLI probes, or model-picker callback flows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | telegram-live-e2e |
| description | OpenClaw-specific checklist for Telegram live verification. Use when validating Telegram behavior against a live bot, especially thread/topic behavior, runtime ownership, userbot CLI probes, or model-picker callback flows. |
Use this skill only for live Telegram verification in this repository.
Do not use it as the default E2E path for non-Telegram bugs. For most browser, tool-routing, or local agent issues, use the local OpenClaw/browser validation flow first and bring in Telegram only when the Telegram bot/runtime itself is part of the feature or the failure.
This skill exists because Telegram validation here has two failure classes:
Do not skip the preflight.
docs/agent-guides/telegram-live.mdscripts/telegram-e2e/README.mddocs/agent-guides/runtime-ops.md when the shared gateway or LaunchAgent is involvedWhen progress/status/final/TTS behavior is under test, also read
docs/agent-guides/telegram-progress-proof.md before running live proof.
Before trusting any Telegram result, print:
branch=<branch>runtime_worktree=<absolute-path>runtime_commit=<sha>current_lane_bot=<bot username if known>Then prove:
HEADUse the repo-local CLI first:
openclaw telegram-user precheck ...openclaw telegram-user send ...openclaw telegram-user read ...openclaw telegram-user wait ...Use lower-level scripts only when the CLI path is missing the required feature.
When a live proof creates a Telegram forum topic, record the returned
topic_anchor and every message id created during the proof. Cleanup must be
bounded to that topic anchor and the proof's exact message ids only. Do not run
broad history deletion to remove a topic.
For temporary test topics, prefer:
openclaw telegram-user topic-delete --chat <forum-chat> --topic-anchor <topic_anchor> --json
Use exact message deletion only as a fallback when topic deletion fails or the
local checkout does not yet expose topic-delete. If falling back, report the
remaining topic anchor plainly so a follow-up can remove it. Do not claim cleanup
is complete when an empty test topic remains.
Do not treat text-command success as callback success.
For model switching, think in separate lanes:
/model openai-codex/gpt-5.4/modelIf the feature relies on buttons, validate the button path explicitly.
For Telegram callback/session bugs, validate both:
If it only works before restart, the bug is not fixed.
message_thread_iddirect_messages_topic.topic_idreply_to_msg_idreply_to_top_idIf those are missing, you are debugging Telegram blind.
Use when the user asks to use a consumer integration that is not set up yet: WhatsApp as Me, Email, Google Workspace, Apple Notes, Apple Reminders, Telegram as Me, Google Maps Search, or creative audio. Route here only when the right integration exists but is blocked by missing login, OAuth, QR pairing, permissions, local dependency setup, configuration, or API credentials, and the response should guide setup in product language instead of dumping CLI commands.
Use for Google Workspace requests tied to Gmail, Google Calendar, Drive, Docs, Sheets, or Contacts, especially when the user explicitly mentions Google or needs cross-surface Google account access. Prefer this over generic email skills when the task is clearly in the Google ecosystem.
Use when the user asks to triage messages, emails, chats, inboxes, unread messages, recent messages, open replies, who they owe replies to, outreach, or reply drafting across one or more channels such as WhatsApp, Telegram, Gmail/email, Slack, Signal, iMessage, browser portals, or files. For broad sweeps, first produce a scoped prioritized triage list; for one known target, use single-thread draft mode. Always require user approval before any external reply/send.
Use for generic email tasks on connected mail accounts: search, read, summarize, draft, reply, forward, send, and organize email over IMAP/SMTP. This is the better match for normal mailbox work that is not specifically a Gmail or Google Workspace request.
Use for Telegram-as-me requests on this Mac: reading, sending, replying, or waiting as the user's real Telegram account. Do not use it for the normal Telegram bot channel, BotFather setup, or generic bot onboarding.
Send WhatsApp messages to other people or search/sync WhatsApp history via the wacli CLI (not for normal user chats).