configure

Configure the Discord bot token and review channel access policy settings.

2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/ghoshsam/claude-code-skills --skill configure-ghoshsam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure
Source: https://github.com/ghoshsam/claude-code-skills/tree/main/skills/discord/configure
Command: npx skills add https://github.com/ghoshsam/claude-code-skills --skill configure-ghoshsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a Discord bot channel requires managing a bot token and understanding who is allowed to reach you, which is easy to misconfigure or leave insecurely open. ## Core Features & Use Cases - Token Management: Save, update, or clear the Discord bot token stored in ~/.claude/channels/discord/.env. - Access Policy Review: Inspect access.json to see the DM policy, allowlisted senders, pending pairing codes, and opted-in guild channels. - Guided Lockdown: Get proactive guidance to move from the temporary pairing policy to a locked-down allowlist policy once all intended users are added. - Use Case: You paste a new Discord bot token from the Developer Portal; the skill saves it, shows your current access state, and tells you exactly what to do next to secure the channel. ## Quick Start Ask the assistant to configure Discord with your bot token, or run it with no arguments to check the current channel status and access policy.

Frequently Asked Questions about configure

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

FAQPage Schema
How do I set up a Discord bot token for my channel?

Generate a token in the Discord Developer Portal under Bot → Reset Token, then pass it to the configure command. The token is written to ~/.claude/channels/discord/.env as DISCORD_BOT_TOKEN and read by the server at boot.

How do I check who can reach me through my Discord bot?

Run the configure command with no arguments to see the current DM policy, allowlisted senders, pending pairing codes, and opted-in guild channels read from access.json. A missing file means default settings: pairing policy with an empty allowlist.

What is the difference between pairing and allowlist policy in Discord access control?

Pairing lets unknown users DM the bot and receive a code you approve to capture their Discord ID. Allowlist is the locked state where only listed snowflake IDs can reach you; pairing should be turned off once everyone is added.

Why is my new Discord bot token not taking effect?

The server reads the .env file only once at boot, so token changes require a session restart or /reload-plugins. Access policy changes in access.json are re-read on every inbound message and take effect immediately.

How do I remove a Discord bot token from the configuration?

Run the configure command with the clear argument to delete the DISCORD_BOT_TOKEN line from the .env file, or the entire file if that is the only line. Restart the session afterward since the server caches the token at boot.