configure

Store Discord bot tokens and audit channel access policies locally.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/angrybeagles/weather-dashboard --skill configure-angrybeagles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure
Source: https://github.com/angrybeagles/weather-dashboard/tree/main/.claude/plugins/marketplaces/claude-plugins-official/external_plugins/discord/skills/configure
Command: npx skills add https://github.com/angrybeagles/weather-dashboard --skill configure-angrybeagles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams securely set up Discord channels by saving the bot token and reviewing access policies.

Core Features & Use Cases

  • Token management: securely store bot tokens in a local config path and orient access policy.
  • Access policy review: surface current DM policy, allowlist, and paired users.
  • Guided setup: step-by-step setup flow to configure channels, permissions, and token handling.

Quick Start

Run /discord:configure <token> with your bot token to initialize the channel and review access policy.

Frequently Asked Questions about configure

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

FAQPage Schema
How do I securely store a Discord bot token for channel access configuration?

Discord bot token storage saves credentials to a local config path at ~/.claude/channels/discord, orienting access policy and enforcing secure allowlisting during the setup flow.

What does a Discord access policy audit check during channel setup?

An access policy audit surfaces the current DM policy, active allowlist, and paired users, allowing you to verify who can reach the bot and enforce secure channel restrictions.

How do I transition a Discord channel from a pairing state to a locked allowlist?

Transitioning to a locked allowlist requires reading and writing the local environment config to review paired users, then enforcing access restrictions to lock down bot configuration.

Do I need any dependencies to configure Discord channel access?

No external dependencies are required; the configuration flow only needs local read and write access to the ~/.claude/channels/discord environment path to store tokens and audit access.

What is the best way to review paired users and DM policy for a Discord bot?

The best way to review paired users and DM policy is running a guided access policy review, which audits current channel permissions and surfaces who can actively reach the bot.

Why does my Discord channel configuration require token management during onboarding?

Token management is required during onboarding to securely initialize the channel, paste the bot token, verify access permissions, and transition from open pairing to a locked allowlist.