Configure
- 1.9k installs
- 32.9k repo stars
- Updated July 31, 2026
- anthropics/claude-plugins-official
Stores Discord bot token and reads/enforces access policy rules from local config files; guides lockdown from pairing to allowlist.
About
This skill manages Discord bot token storage and access control for Claude agent deployments. Developers use it to register a bot token with the local Claude server, review who can reach the agent via Discord DM, and enforce access policies (pairing or allowlist). Core workflows: initialize with a token, check current configuration status, transition from permissive pairing mode to locked allowlist mode, and clear credentials. The skill reads/writes `.env` and `access.json` files in `~/.claude/channels/discord/`, guides users toward secure allowlist lockdown, and explains next steps based on current state.
- Save Discord bot token to ~/.claude/channels/discord/.env with file permissions (chmod 600)
- Check configuration status: token presence, DM policy (pairing vs allowlist), allowed senders, pending pairing codes, op
- Display complete access state and guide users toward allowlist lockdown from permissive pairing mode
- Support token operations: set with <token> argument, clear with 'clear' argument, or show status with no args
- No server restart needed for policy changes (access.json re-read per message); token changes require session restart
Configure by the numbers
- 1,881 all-time installs (skills.sh)
- +279 installs in the week ending Jul 29, 2026 (Skillselion tracking)
- Ranked #189 of 2,725 Automation & Workflows skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
configure capabilities & compatibility
No operational cost; requires valid Discord bot token (free tier available).
- Capabilities
- read and write discord bot token to .env · display full configuration status (token, policy · parse and enforce dm policy rules (pairing vs al · advise users on transition from pairing to locke · clear stored credentials
- Use cases
- orchestration
- Platforms
- macOS · Windows · Linux · WSL
- Runs
- Runs locally
- Pricing
- Free
npx skills add https://github.com/anthropics/claude-plugins-official --skill configureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.9k |
|---|---|
| repo stars | ★ 32.9k |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 31, 2026 |
| Repository | anthropics/claude-plugins-official ↗ |
What it does
Store Discord bot credentials and configure access policy rules for incoming messages.
Who is it for?
Developers deploying Claude agents to Discord who need credential management and fine-grained access control.
Skip if: Users deploying without local file system access; those not using Discord as a message channel.
When should I use this skill?
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.
What you get
Bot token persists with secure file permissions; access policy is enforced on every message; user understands current configuration and next steps.
- Stored bot token in .env file
- Readable access.json showing policy and allowed senders
- Confirmation and next-step guidance
By the numbers
- Supports 'pairing' and 'allowlist' modes for access policy
- Reads access.json state on every inbound message for zero-restart policy updates
- Enforces file permissions (chmod 600) on sensitive .env file
Files
/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:
1. Token — check ~/.claude/channels/discord/.env for DISCORD_BOT_TOKEN. Show set/not-set; if set, show first 6 chars masked.
2. 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
3. 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:
1. Read the allowlist. Tell the user who's in it. 2. Ask: "Is that everyone who should reach you through this bot?" 3. 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. 4. 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>`." 5. 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." 6. 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
1. 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. 2. mkdir -p ~/.claude/channels/discord 3. Read existing .env if present; update/add the DISCORD_BOT_TOKEN= line, preserve other keys. Write back, no quotes around the value. 4. chmod 600 ~/.claude/channels/discord/.env — the token is a credential. 5. 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
.envonce at boot. Token changes need a session restart
or /reload-plugins. Say so after saving.
access.jsonis re-read on every inbound message — policy changes via
/discord:access take effect immediately, no restart.
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.577k39.1k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.471kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.471kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.470kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.470kLark Vc AgentGive their coding agent the ability to read, create, and update documents, tasks, and wiki pages inside Feishu (Lark).415kHow it compares
Pick configure for Claude-native Discord channel wiring; pick generic Discord bot framework skills when building bots outside Claude's channel directory.
FAQ
Where is the bot token stored and how is it protected?
Token is written to ~/.claude/channels/discord/.env with chmod 600 (readable/writable by owner only). Server reads it once at boot.
What is the difference between pairing and allowlist policies?
Pairing is temporary: users DM the bot, receive a code, and you approve each with /discord:access pair <code>. Allowlist is locked: only pre-approved Discord user IDs can reach the bot. Always migrate to allowlist once everyone is captured.
Do I need to restart the server after changing configuration?
Token changes require session restart or /reload-plugins. Access policy changes (via /discord:access) take effect immediately—no restart needed.
Is Configure safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.