configure

anthropics/claude-plugins-official

Set up Discord bot token and configure channel access policy.

What is configure?

Configures the Discord channel by saving your bot token and managing access control. Use this when you have a Discord bot token to register, need to set up channel access, or want to review your current configuration and security policy.

Save and validate Discord bot tokens to `~/.claude/channels/discord/.env`
Display current token status (set/unset) and access policy configuration
Read and show allowed senders, pending pairings, and opted-in guild channels
Guide users through pairing mode to capture Discord user IDs
Lock down access by switching from pairing mode to allowlist policy
Remove or clear stored tokens securely

How to install configure

npx skills add https://github.com/anthropics/claude-plugins-official --skill configure

Prerequisites

A Discord bot token from the Developer Portal (Bot → Reset Token)
Access to the file system to store configuration in `~/.claude/channels/discord/`

Claude Code

Cursor

Windsurf

Cline

How to use configure

1.Run `/discord:configure` with no arguments to check current status and see what's configured
2.If you have a bot token, run `/discord:configure <token>` to save it
3.Review the displayed access policy: note whether you're in pairing or allowlist mode
4.If in pairing mode, DM your bot to capture your own Discord ID first
5.Add other users by having them DM the bot and approving with `/discord:access pair <code>`, or by copying their User IDs directly
6.Once all users are added, run `/discord:access policy allowlist` to lock down access and prevent new pairings
7.Run the skill again to confirm the final configuration is secure

Use cases

Good for

Initial setup: paste your bot token from the Discord Developer Portal to register the channel
Review configuration: run with no arguments to see current token status and who can reach you
Add users: use pairing mode to capture Discord IDs from new users, then lock the allowlist
Migrate to allowlist: transition from temporary pairing mode to permanent allowlist-based access control
Troubleshoot access: verify token is set and check which users are currently allowed

Who it's for

Discord bot owners setting up Claude integration
Users managing access control for a Discord channel
Developers configuring multi-user Discord bots with security policies

configure FAQ

What's the difference between pairing mode and allowlist mode?

Pairing mode is temporary: users DM the bot and you approve each one by code. Allowlist mode is locked: only pre-approved Discord user IDs can reach you. Pairing is meant to capture IDs you don't know; once everyone is added, switch to allowlist for security.

How do I get my Discord user ID?

Enable Developer Mode in Discord (User Settings → Advanced), then right-click your name or avatar and select Copy User ID. You can also DM the bot and approve yourself via pairing code.

Do I need to restart anything after saving a token?

The bot token is read at server boot. If you change the token, you'll need to restart your session or run `/reload-plugins` for the change to take effect. Access policy changes take effect immediately.

What happens if I clear the token?

Running `/discord:configure clear` removes the stored bot token. The Discord channel will no longer be able to connect until you save a new token.

Is pairing mode secure?

Pairing mode requires explicit approval for each new user, but it's not a long-term security model. Always transition to allowlist mode once you've captured all the IDs you need, so no one else can trigger new pairing codes.

Full instructions (SKILL.md)

Source of truth, from anthropics/claude-plugins-official.

name: configure description: Set up the Discord channel — save the bot token and review access policy. Use when the user pastes a Discord bot token, asks to configure Discord, asks "how do I set this up" or "who can reach me," or wants to check channel status. user-invocable: true allowed-tools:

Read
Write
Bash(ls *)
Bash(mkdir *)

/discord:configure — Discord Channel Setup

Writes the bot token to ~/.claude/channels/discord/.env and orients the user on access policy. The server reads both files at boot.

Arguments passed: $ARGUMENTS

Dispatch on arguments

No args — status and guidance

Read both state files and give the user a complete picture:

Token — check ~/.claude/channels/discord/.env for DISCORD_BOT_TOKEN. Show set/not-set; if set, show first 6 chars masked.
Access — read ~/.claude/channels/discord/access.json (missing file = defaults: dmPolicy: "pairing", empty allowlist). Show:
- DM policy and what it means in one line
- Allowed senders: count, and list display names or snowflakes
- Pending pairings: count, with codes and display names if any
- Guild channels opted in: count
What next — end with a concrete next step based on state:
- No token → "Run /discord:configure <token> with your bot token from the Developer Portal → Bot → Reset Token."
- Token set, policy is pairing, nobody allowed → "DM your bot on Discord. It replies with a code; approve with /discord:access pair <code>."
- Token set, someone allowed → "Ready. DM your bot to reach the assistant."

Push toward lockdown — always. The goal for every setup is allowlist with a defined list. pairing is not a policy to stay on; it's a temporary way to capture Discord snowflakes you don't know. Once the IDs are in, pairing has done its job and should be turned off.

Drive the conversation this way:

Read the allowlist. Tell the user who's in it.
Ask: "Is that everyone who should reach you through this bot?"
If yes and policy is still pairing → "Good. Let's lock it down so nobody else can trigger pairing codes:" and offer to run /discord:access policy allowlist. Do this proactively — don't wait to be asked.
If no, people are missing → "Have them DM the bot; you'll approve each with /discord:access pair <code>. Run this skill again once everyone's in and we'll lock it." Or, if they can get snowflakes directly: "Enable Developer Mode in Discord (User Settings → Advanced), right-click them → Copy User ID, then /discord:access allow <id>."
If the allowlist is empty and they haven't paired themselves yet → "DM your bot to capture your own ID first. Then we'll add anyone else and lock it down."
If policy is already allowlist → confirm this is the locked state. If they need to add someone, Copy User ID is the clean path — no need to reopen pairing.

Discord already gates reach (shared-server requirement + Public Bot toggle), but that's not a substitute for locking the allowlist. Never frame pairing as the correct long-term choice. Don't skip the lockdown offer.

`<token>` — save it

Treat $ARGUMENTS as the token (trim whitespace). Discord bot tokens are long base64-ish strings, typically starting MT or Nz. Generated from Developer Portal → Bot → Reset Token; only shown once.
mkdir -p ~/.claude/channels/discord
Read existing .env if present; update/add the DISCORD_BOT_TOKEN= line, preserve other keys. Write back, no quotes around the value.
chmod 600 ~/.claude/channels/discord/.env — the token is a credential.
Confirm, then show the no-args status so the user sees where they stand.

`clear` — remove the token

Delete the DISCORD_BOT_TOKEN= line (or the file if that's the only line).

Implementation notes

The channels dir might not exist if the server hasn't run yet. Missing file = not configured, not an error.
The server reads .env once at boot. Token changes need a session restart or /reload-plugins. Say so after saving.
access.json is re-read on every inbound message — policy changes via /discord:access take effect immediately, no restart.