What does this skill do, and when should you use it?
This skill configures a Discord channel connection and reports its access state. It saves the bot token in Claude Code’s Discord channel directory and reads the access policy, allowlist, pending pairings, and opted-in guild channels. It encourages using pairing temporarily to collect user IDs, then switching to an allowlist for tighter control. Token changes require a session restart or `/reload-plugins`, while access-policy changes take effect immediately.
With no arguments, it reads ~/.claude/channels/discord/.env and access.json, checks whether the token is set, shows the first six masked token characters, reports the DM policy, allowed senders, pending pairings, and opted-in guild channels, and recommends a next step. With a token argument, it creates the Discord channel directory, updates or adds DISCORD_BOT_TOKEN, preserves other environment variables, writes the value without quotes, and sets the file mode to 600. With clear, it removes the token line or deletes the file when that is the only line.
- A user who wants to reach an assistant through Discord and has just obtained a bot token.
- A user who needs to inspect the current DM policy, allowlist, pending pairings, or opted-in guild channels.
- An administrator who wants to move from temporary pairing access to a defined allowlist.
- A user who needs to remove locally stored Discord bot credentials.
How do you install this skill?
- Do not expose the Discord bot token in chat history, shell history, or logs; confirm that the host will not record the argument.
- Add explicit confirmation, format validation, and recoverable backup before saving the token, and disclose that the server will use it to connect to Discord.
- Pairing temporarily broadens reachability; verify the allowlist and switch to allowlist policy after setup.
- The static material does not establish Discord reachability from mainland-China networks or prove successful end-to-end configuration.
- Shell / CLI
- Local filesystem
Discord bot token
The skill is located at external_plugins/discord/skills/configure/SKILL.md in the Discord skill bundle within anthropics/claude-plugins-official. The collection can be installed in Claude Code with /plugin install {plugin-name}@claude-plugins-official, or discovered through /plugin > Discover. The source does not provide the specific {plugin-name}, so a more specific installation command cannot be verified.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/anthropics/claude-plugins-official.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/external_plugins/discord/skills/configure" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Run /discord:configure to inspect token and access status. Run /discord:configure <token> to save a Discord bot token obtained from Developer Portal → Bot → Reset Token. After saving, restart the session or run /reload-plugins. Run /discord:configure clear to remove the token. Pairing and access-policy changes use /discord:access pair <code>, /discord:access allow <id>, and /discord:access policy allowlist.
What are this skill's strengths and limitations?
- Combines token storage, status inspection, and access-policy guidance.
- Preserves existing environment variables and restricts credential-file permissions to 600.
- Explicitly guides users from temporary pairing toward an allowlist.
- The access policy file is reread for every inbound message.
- Depends on Claude Code-specific `/discord:*` commands, `$ARGUMENTS`, and `allowed-tools` configuration.
- Token changes do not take effect automatically and require a session restart or plugin reload.
- The source does not document broader Discord server deployment or troubleshooting.
- It covers configuration and access guidance, not the complete Discord bot implementation.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Discord Channel Configurator this page ✓ Anthropic · Official | 47 · Use with care | ★ 38k | 11d ago | Apache-2.0 |
| Claude-Mem OpenClaw Persistent Memory Plugin | 59 · Recommended | ★ 101k | 12d ago | Apache-2.0 |
| Discord Channel Access ✓ Anthropic · Official | 53 · Use with care | ★ 38k | 11d ago | Apache-2.0 |
| Azure AI Gateway Governance ✓ Microsoft · Official | 55 · Use with care | ★ 2.7k | 3mo ago | MIT |
| Google Cloud gcloud CLI Safety Skill ✓ Google · Official | 51 · Use with care | ★ 21k | 11d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill limits tools to Read, Write, mkdir, and constrained Bash, stores the token with mode 600, and promotes pairing to an allowlist. However, it accepts the token directly as user arguments without explicit confirmation, validation, backup, or rollback, and does not fully disclose how the server reads or transmits the credential to Discord, so points are deducted.
The dispatch branches, missing-file semantics, reload requirement, and immediate access-policy behavior are described clearly. However, there is no test suite, execution evidence, abnormal-input handling, or diagnostic failure feedback; the clear path also lacks documented failure handling, so the static score remains conservative.
The triggering conditions and the no-argument, token, and clear paths are clearly defined for Discord setup. Boundaries, non-fit cases, platform requirements, Chinese-language support, and mainland-China network reachability are not addressed, and the token-format guidance is only heuristic, so points are deducted.
The document has clear sections for dispatch, permissions, status reporting, and next actions; the repository also supplies an Apache-2.0 license and official maintenance provenance. It lacks versioning, changelog, dedicated examples, FAQ, explicit maintenance ownership/update path, and dependency notes, so the score is reduced.
The skill can save or remove a Discord bot token, report access state, and guide the user toward a tighter policy, giving it clear core utility. However, outcomes depend on the external Discord service and separate /discord:access behavior, with no complete result verification or recovery workflow; static evidence cannot establish end-to-end usability, so the score stays below the static ceiling.
The SKILL.md gives auditable descriptions of key paths and configuration files, and repository CI provides some maintenance signal. There are no skill-specific tests, runtime logs, third-party execution results, or independent corroboration, and the supplied CI does not cover this skill's key paths, so evidence remains limited.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →