Menu
Configure the Discord channel — save bot token, set auto-thread, embed options.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Manage Discord channel access — guild/channel allowlists, DM policy, user/role allowlists.
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
Set up the Telegram channel — save the bot token and review access policy. Use when the user pastes a Telegram bot token, asks to configure Telegram, asks "how do I set this up" or "who can reach me," or wants to check channel status.
ALWAYS invoke this skill when user says 'browser [site]', 'open [site]', or asks to navigate to a website. Never call MCP browser tools directly.
Show detailed status, version info, and update availability for an installed app.
Scan Dockerfile(s) in the current directory and generate a draft app.yaml for the gateway app store.
Based on SOC occupation classification
| name | discord-configure |
| description | Configure the Discord channel — save bot token, set auto-thread, embed options. |
| user-invocable | true |
Use this skill to set up the Discord channel for an agent.
/gateway:discord-configure token <BOT_TOKEN>
Writes DISCORD_BOT_TOKEN=<token> to $DISCORD_STATE_DIR/.env.
Add to the agent's .env file:
DISCORD_BOT_TOKEN=<your-bot-token>
DISCORD_STATE_DIR=~/.claude-gateway/agents/<id>/.discord-state
DISCORD_DM_POLICY=disabled # open | allowlist | disabled
DISCORD_GUILD_ALLOWLIST= # comma-separated guild IDs (empty = all)
DISCORD_CHANNEL_ALLOWLIST= # comma-separated channel IDs (empty = all)
DISCORD_AUTO_THREAD=false # create thread per conversation
DISCORD_USE_EMBEDS=false # use embeds for long responses
Scope note. DMs and guilds are gated separately: DMs by
dmPolicy+pairing, guilds bygroupPolicy+guildAllowlist+requireMention(see/gateway:discord-access). The intent and permissions above are the platform-level prerequisites — the access lists only matter once messages actually reach the bot.
Parse the subcommand and act accordingly:
token <value> — write .env file to DISCORD_STATE_DIRshow — display current env vars (mask the token)check — verify the bot can connect (call discord_reply to a test channel if provided)Confirm each action and display what was changed.