openclaw-agent-claw-config

Telegram group/forum provisioning and management. USE WHEN: inviting bots to a group, promoting bots to admin, creating groups/forums, creating topics, sending messages as user or bot, checking bot permissions. DON'T use raw curl/Telegram API for these — this skill wraps safe Telethon (user) and Bot API (bot) scripts. Also use when: you need to add/remove/manage members in a Telegram group where you have admin rights. Triggers on: invite bot, add bot to group, promote bot, create topic, telegram group setup, forum setup. Safety: user API (MTProto) = high-risk, bot API = low-risk, never mix.

A cognitive protocol for safely managing and auditing OpenClaw application upgrades. Analyzes configuration-level risks (schema, defaults) and runtime-level behavioral shifts (routing, sessions, streaming) using semantic changelog analysis to prevent silent breaking changes.

Restore or migrate OpenClaw session history from a source session to a target session. Use when recovering lost context, migrating sessions after Telegram topic migration, or transferring conversation history between sessions. WARNING This is a HIGH-RISK operation that modifies session files directly.

OpenClaw configuration management safety protocol and change reporting. Use when modifying OpenClaw configuration that affects runtime behavior: (1) editing openclaw.json (bindings, channels, agents), (2) changing workspace prompt files (SOUL.md, AGENTS.md, IDENTITY.md), (3) restarting gateway or agents, (4) installing/removing skills or tools, or (5) any action that may impact message routing or agent behavior.

Create or review OpenClaw skills for the claw-config agent. Default mode drafts a new skill (proposal-only) with docs-first diagnosis, change control, and claw-config safety constraints; review mode audits an existing skill for correctness and safety.

Safely simplify OpenClaw `bindings` (routing rules) while preserving behavior. Use when bindings are redundant (per-topic spam), when accounts are exclusive to a single agent, or when you need to reduce binding count without breaking routing/activation.

Cross-group posting via proxy bot. Route messages from a high-privileged agent (main) to a low-privileged bot account in another group/channel. Use message tool with accountId to specify which bot sends. Covers warm-up strategies for topics/threads and troubleshooting why proxy messages don't appear.

End-to-end checklist + diagnosis playbook for onboarding the OpenClaw Telegram bot into a new Telegram group (including Topics). Use when someone says they added the bot to a group but it doesn’t reply, asks for the group chat_id, wants to route the group to a specific agent (main vs restricted bot), or you see symptoms like "no session created" / "not-allowed" / mention gating confusion.

Enforce “docs-first, code-second” behavior for OpenClaw configuration/behavior questions. Use when answering questions about OpenClaw config options, routing, precedence, CLI behavior, outages, or implementation details. Prefer official docs; if unclear or version-sensitive, confirm in source code (rg). Fall back to asking the user to run copy-paste commands when local repo/tools are unavailable.

Debug Telegram forum topic routing and control-plane message injection (sessions_send) in OpenClaw, including seeding topics (message_thread_id), verifying who sends (deliveryContext.accountId), diagnosing stuck/pending announces, and using diagnostics flags (telegram.http) to confirm sendMessage failures.

Debug and explain Telegram “bot not responding” outages in OpenClaw (DM vs group, requireMention vs dmPolicy/pairing vs token 409 vs network fetch failures vs LLM timeouts). Use when diagnosing why a Telegram bot suddenly stops replying, when building a timeline from gateway.log/gateway.err.log, or when enabling temporary diagnostics flags (telegram.http) to capture root cause.