discord-intent-applicationlisted

Helps write the justification text for Discord Developer Portal privileged intent applications (Message Content, Server Members, Presence) for a specific bot. Takes a plain-text description of the bot's functionality and/or an uploaded/local codebase, screens the bot's features against Discord's known rejection triggers, and writes one txt file per needed intent containing the exact answer to paste into the "What do you need this intent for?" field. Only use this skill when the user explicitly asks for help with a Discord privileged intent application, an intent request/justification, or filling out the Discord developer portal's intent form — do not trigger this for general Discord bot coding, feature planning, or unrelated Discord questions.
The-LukeZ/discord-intent-application · ★ 2 · AI & Automation · score 73

Install: claude install-skill The-LukeZ/discord-intent-application

# Discord Privileged Intent Application Writer Writes the justification text Discord asks for when a bot developer requests a privileged gateway intent (Message Content, Server Members, Presence) in the Developer Portal. The goal is an application that gets **approved**: specific, minimal, tied to real shipped features, and written so a reviewer with zero technical Discord/bot knowledge can follow it. ## Reference files - `references/rules.md` — the user's own compiled rules for what makes an application succeed or fail. Read this in full before drafting anything. This is the authoritative source for tone, disqualifying use cases, and wording requirements. - `references/alternatives.md` — paraphrased summary of Discord's official guidance on non-privileged alternatives (slash commands, context menus, components, modals, REST lookups) per intent. Use this to check whether a feature genuinely needs the intent at all. Read both files before Step 2. ## Inputs Gather whichever of these the user provides (ask only if genuinely missing/ambiguous — don't block on it if there's enough to work from): 1. A plain-text description of what the bot does (required in some form). 2. Optionally, a codebase — a path, repo, or uploaded files. If code is available (this is most useful when running inside Claude Code with direct filesystem access), scan it for evidence of what the bot actually does with each intent, e.g.: - Message Content: handlers reading `message.content