Perform Task
telegramdesktop/tdesktop
Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results.
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
MITAuto-check passed
Install Configure Channel
$ npx skills add openclaw/openclaw --skill configure-channel -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openclaw/openclaw configure-channel --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/custodian-skills/configure-channel .claude/skills/configure-channel && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "configure-channel" agent skill from https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channel into .claude/skills/configure-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure-channel", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channelType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openclaw/openclaw --skill configure-channel -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openclaw/openclaw configure-channel --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/custodian-skills/configure-channel .agents/skills/configure-channel && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "configure-channel" agent skill from https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channel into .agents/skills/configure-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure-channel", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/openclaw --skill configure-channel -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openclaw/openclaw configure-channel --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/custodian-skills/configure-channel .cursor/skills/configure-channel && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "configure-channel" agent skill from https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channel into .cursor/skills/configure-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure-channel", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openclaw/openclaw.git --path custodian-skills/configure-channel--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openclaw/openclaw --skill configure-channel -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openclaw/openclaw configure-channel --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/custodian-skills/configure-channel .gemini/skills/configure-channel && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "configure-channel" agent skill from https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channel into .gemini/skills/configure-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure-channel", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openclaw/openclaw configure-channelInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openclaw/openclaw --skill configure-channel -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/custodian-skills/configure-channel .github/skills/configure-channel && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "configure-channel" agent skill from https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channel into .github/skills/configure-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure-channel", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openclaw/openclaw --skill configure-channel -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openclaw/openclaw configure-channel --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/custodian-skills/configure-channel .opencode/skills/configure-channel && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "configure-channel" agent skill from https://github.com/openclaw/openclaw/tree/main/custodian-skills/configure-channel into .opencode/skills/configure-channel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure-channel", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
configure-channel- GitHub stars
- 392k
- Token cost
- ~946 tokens
- SKILL.md length
- 400 words
- Files
- 1
- Skills in repo
- 96
- Repo updated
- First seen
- Licence
- MIT
At a glance
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
- SKILL.md covers Gather, Mutate, Repair and Prove, plus 1 more section
- Calls jq; needs TELEGRAM_BOT_TOKEN
What it does
Configure Channel is an agent skill from openclaw/openclaw. Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with Telegram. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.
Example prompts
- “/configure-channel”
Requirements
- A credential in TELEGRAM_BOT_TOKEN
What it can do on your machine
Read from SKILL.md and the folder at commit f8e594e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jq
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.openclaw.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
TELEGRAM_BOT_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Configure Channel loads about 946 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 400 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openclaw/openclaw at commit f8e594e, republished under its MIT licence (© openclaw). 400 words, ~946 tokens.
Download SKILL.mdSave it as
.claude/skills/configure-channel/SKILL.md (or your agent's skills folder).- name
- configure-channel
- description
- Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
Configure a channel
Never print or persist secret values; channel tokens enter config only as SecretRefs, or through the in-session connect_channel flow where the operator types the secret into a masked prompt. Never hand-edit config files on disk. Every run ends with the observable Prove result or an exact explanation of why it could not be proven.
Gather
openclaw channels list --all
openclaw channels status
openclaw config get channels --json # "Config path not found" is normal before first setupConfirm the exact config path before writing — key names differ per channel (channels.telegram.botToken, channels.discord.token, ...):
openclaw config schema --json | jq '.properties.channels.properties.telegram'Mutate
Confirm the intended account and access changes with the operator before writing. Preserve existing approved allowlist entries, dmPolicy, and groupPolicy unless their replacement or change is explicitly approved; never broaden access to make a check pass.
Preferred shell path — token staged as an env var on the gateway process or in a 0600 file, wired as a SecretRef (Telegram example):
openclaw config set channels.telegram.botToken --ref-provider default --ref-source env --ref-id TELEGRAM_BOT_TOKENWith the bot connected and DM policy pairing, ask the operator to DM it. Read Your Telegram user id in the pairing reply, or run openclaw logs --follow and read senderUserId in that sender's telegram pairing request entry. Stop following once captured; keep unrelated logs private. If the current policy prevents this flow, use an already verified ID or report the discovery blocker; do not broaden access.
Use the numeric Telegram user ID, not a phone number, username, chat/group ID, or bot ID. In this single-user example, 123456789 is a placeholder: replace it with the verified, approved user ID and retain any other approved entries.
openclaw config set channels.telegram.allowFrom '["123456789"]' --strict-jsonMulti-field changes in one validated write:
openclaw config patch --stdin <<'JSON'
{ channels: { telegram: { enabled: true, groupPolicy: "allowlist" } } }
JSONIn-session alternative: call the connect_channel tool action with the channel id — the operator enters the token in a masked prompt, never in chat. Avoid openclaw channels add --token <value>: it puts the secret in argv and process listings.
Show full SKILL.md (118 more words)Show less
Repair
openclaw doctor --lint
openclaw channels status --probedoctor --lint can exit 1 for findings: read the report and continue the remaining checks. Ordinary doctor and doctor --non-interactive can write config/state; do not use them for diagnosis before approval. Apply openclaw doctor --fix --non-interactive only after explicit approval, then re-check status.
Prove
Send one real, clearly labeled test message and confirm delivery from the command result (use --dry-run first to inspect the payload):
openclaw message send --channel telegram --target <chatId> --message "OpenClaw channel test — please ignore" --dry-run
openclaw message send --channel telegram --target <chatId> --message "OpenClaw channel test — please ignore"If sending fails, report the exact account, permission, destination, or network blocker without exposing credentials.
Report
State the channel and account changed, the exact config paths written (never values), the test destination, and the observed delivery result. List any remaining operator action.
Further reference: https://docs.openclaw.ai/channels/telegram (and the matching page for other channels)
© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in custodian-skills/configure-channel of openclaw/openclaw.
Open the folder on GitHubat commit f8e594e
Compare with similar skills
Configure Channel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Configure Channel this skillopenclaw/openclaw | 392k | — | ~946 | Automated safety check: Pass | MIT | |
| Perform Tasktelegramdesktop/tdesktop | 33k | 2 repos | ~3k | Automated safety check: Pass | GPL-3.0 | |
| Custom Mode Creator for claude-memthedotmack/claude-mem | 99k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Dependency Watchtelegramdesktop/tdesktop | 33k | — | ~2.2k | Automated safety check: Pass | GPL-3.0 | |
| Continuetelegramdesktop/tdesktop | 33k | 2 repos | ~9.4k | Automated safety check: Pass | GPL-3.0 | |
| Process InboxTDesktop-x64/tdesktop | 3k | 1 repos | ~4.3k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Custom Mode Creator for claude-mem
thedotmack/claude-mem
Walks you through creating, installing and verifying a custom claude-mem mode, including note types, tags and optional Telegram alerts for chosen memories.
Dependency Watch
telegramdesktop/tdesktop
Audit Telegram Desktop dependencies on freshly fetched origin/dev for releases and security fixes, including upstream lag and backport candidates in patched forks.
Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
Process Inbox
TDesktop-x64/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
Process Inbox
telegramdesktop/tdesktop
Process the local ignored ai-tdesktop inbox into durable, independently testable Telegram Desktop task records while task execution worktrees remain active.
More from openclaw/openclaw
All 96 skills in this repoModel Usage
openclaw/openclaw
Summarize CodexBar local cost logs by model for Codex or Claude, including current or full breakdowns.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Feishu Doc
openclaw/openclaw
Feishu document read/write workflows. An agent skill from openclaw/openclaw.
Tmux
openclaw/openclaw
Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.
Openclaw PR Maintainer
openclaw/openclaw
Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.
Browser Automation
openclaw/openclaw
A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
Related
Works with
Questions about Configure Channel
What does Configure Channel do?
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs. Configure Channel is an agent skill from openclaw/openclaw. Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
How do I install Configure Channel in Claude Code?
Run `npx skills add openclaw/openclaw --skill configure-channel -a claude-code`. Or copy the skill folder (custodian-skills/configure-channel in openclaw/openclaw) into .claude/skills/configure-channel in your project. Claude Code loads it when a task matches its description.
How do I install Configure Channel in Codex?
Run `npx skills add openclaw/openclaw --skill configure-channel -a codex`. Or copy the skill folder (custodian-skills/configure-channel in openclaw/openclaw) into .agents/skills/configure-channel in your project. Codex loads it when a task matches its description.
Can I use Configure Channel in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw --skill configure-channel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configure-channel, .gemini/skills/configure-channel, .github/skills/configure-channel and .opencode/skills/configure-channel in your project.
What does Configure Channel need to run?
Going by SKILL.md and its folder, Configure Channel needs the command-line tools its instructions call (jq) and credentials named TELEGRAM_BOT_TOKEN. Our summary lists: A credential in TELEGRAM_BOT_TOKEN.
Does Configure Channel access the network?
SKILL.md names 1 domain. As links in the text: docs.openclaw.ai. This is read from the text; nothing was executed.
Is Configure Channel safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Configure Channel use?
Configure Channel is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Configure Channel use?
About 946 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Configure Channel?
Skills that share tags, products or a category with Configure Channel: Perform Task (telegramdesktop/tdesktop, 33k stars), Custom Mode Creator for claude-mem (thedotmack/claude-mem, 99k stars), Dependency Watch (telegramdesktop/tdesktop, 33k stars) and Continue (telegramdesktop/tdesktop, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Configure Channel?
openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,504 GitHub stars. The repository holds 96 skills in this directory. The repository was last updated on October 9, 2026.
Source: openclaw/openclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.