OpenClaw Telegram ACP Troubleshooter

Diagnose why Telegram forum topics do not reliably route into OpenClaw ACP sessions backed by codex. 诊断 Telegram 话题为何无法稳定进入 OpenClaw 的 codex ACP 会话。

This skill appears coherent and safe in that it only advises inspecting local OpenClaw state and Telegram-related logs and does not request credentials or install code. Before using: 1) confirm you trust the agent runtime because the troubleshooting steps involve reading files under ~/.openclaw and /tmp/openclaw and running user-level systemctl commands (these logs can contain sensitive info); 2) if you are uncomfortable letting an automated agent read logs, run the listed commands yourself and share only the relevant redacted excerpts; 3) the skill forbids revealing secrets but that is a guideline in the instructions — treat it as your responsibility to avoid pasting tokens or full config dumps into external outputs; 4) because the skill is instruction-only, it won't install anything, but if you publish or mirror it into a shared workspace, ensure the workspace contains the expected OpenClaw layout so the checks make sense.

Type: OpenClaw Skill Name: openclaw-telegram-acp-troubleshooter Version: 1.0.1 The skill bundle is a legitimate troubleshooting tool for diagnosing Telegram integration issues within the OpenClaw ecosystem. It provides clear instructions for an AI agent to inspect service status via 'systemctl' and review local log files (e.g., '~/.openclaw/logs/commands.log'). The bundle includes explicit constraints preventing the disclosure of sensitive environment variables or credentials, and all recommended commands are standard diagnostic tools aligned with the stated purpose.