configure-channel

Configure and verify chat channel integrations using SecretRefs and one-liner commands.

388k|81.5k|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/openclaw/openclaw --skill configure-channel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-channel
Source: https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channel
Command: npx skills add https://github.com/openclaw/openclaw --skill configure-channel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up chat channels like Telegram or Discord requires handling sensitive tokens safely, writing correct config paths, and proving the channel actually works. This Skill enforces a non-interactive, secret-safe workflow that ends with a verified test message.

Core Features & Use Cases

  • Secret-Safe Configuration: Tokens are wired as SecretRefs from environment variables or 0600 files, never passed via argv or written to disk in plaintext.
  • Schema-Aware Writes: Inspects the config schema to confirm exact key names per channel before mutating configuration.
  • End-to-End Prove Step: Sends a labeled test message and reports the observed delivery result, or explains exactly why delivery failed.
  • Use Case: An operator needs to onboard a new Telegram bot for a team deployment. They list channels, set the bot token as a SecretRef, patch group policy, run doctor, and send a test message to confirm delivery.

Quick Start

Configure the Telegram channel using a SecretRef for the bot token and send a labeled test message to verify delivery.

Frequently Asked Questions about configure-channel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a Telegram channel with OpenClaw?

Run `openclaw channels list --all` to inspect existing channels, then set the bot token as a SecretRef using `openclaw config set channels.telegram.botToken --ref-provider default --ref-source env --ref-id TELEGRAM_BOT_TOKEN`. Finish by sending a labeled test message to confirm delivery.

What is the safest way to pass channel tokens to OpenClaw?

Stage the token as an environment variable on the gateway process or in a `0600` file, then wire it as a SecretRef via `openclaw config set`. Avoid `openclaw channels add --token <value>` because it exposes the secret in argv and process listings.

Does OpenClaw support multi-field channel config updates in one write?

Yes. Use `openclaw config patch --stdin` with a JSON payload to apply multiple validated field changes atomically, for example enabling a channel and setting its group policy in a single transaction.

Why does my channel test message fail to deliver?

Run `openclaw doctor --non-interactive` and `openclaw channels status --deep` to surface account, permission, destination, or network blockers. The skill reports the exact failure reason without exposing credentials.

Can I edit OpenClaw channel config files by hand?

No. The skill explicitly forbids hand-editing config files on disk. All mutations must go through `openclaw config set` or `openclaw config patch` so the gateway can validate and persist them correctly.