AI SKILL discord developers
Agent Kaizen skill for Claude Code & Codex: faithful, identifier-preserving reference for the Discord Developer Platform, bots & apps, slash/application commands, interactions & message components, REST API, Gateway (intents/opcodes/events), resources (channels, guilds, webhooks), OAuth2, permissions, embeds, and monetization.
npx -y skills add LevyBytes/AI-SKILL-discord-developersAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when building on the Discord developer platform: bots and apps, slash/application commands and interactions (buttons, select menus, modals, message components), the HTTP/REST API and Gateway (WebSocket) with opcodes, intents, and events, and the REST resources - application, channel, message, guild, user, webhook, emoji, sticker, invite, voice, audit-log, auto-moderation, poll, role-connection, scheduled-event, stage-instance, soundboard, SKU/entitlement/subscription. Also covers OAuth2 and bot authorization, permissions and permission bit flags, embeds, snowflake IDs, rate limits, monetization, Rich Presence, embedded Activities (the Embedded App SDK), and the C/C++ Discord Social SDK. Use this when answering how a Discord endpoint, gateway event, interaction, intent, permission, or object field works, what parameters/JSON an API call takes, or which scope/intent is required. The official Discord developer docs. Not for the end-user Discord app or general server administration.
SKILL.md
2.9 KB, as published. Nobody here has run it
Discord Developer Platform Reference
Original-prose reference for Discord Developer Platform, split into one focused file per subject across 124 reference files. Identifiers (API/type/function names, flags, paths, enums, numbers) are preserved verbatim.
When to use this
Use this skill when the task involves building on Discord - bots/apps, application commands and interactions/components, the REST API and Gateway (intents, opcodes, events), the API resources (channels, messages, guilds, users, webhooks, ...), OAuth2 scopes, permissions and bit flags, embeds, rate limits, monetization, Rich Presence, Activities (Embedded App SDK), and the C/C++ Social SDK.
Workflow
- Open
references/INDEX.md(orreferences/topics.json) and pick the one file that matches. - Read only that file; open another only if the task spans subjects. Grep across files when needed:
rg -n "PATTERN" references/*.md. - Treat every identifier as an exact reference fact - never invent or paraphrase.
Gotchas
Recurring failure modes and what to do instead live in the sibling GOTCHA.md.
References
All depth lives in references/ - start at references/INDEX.md, metadata in references/topics.json. One subject per file.
Official documentation
The official documentation is at https://docs.discord.com/developers/intro - consult it to verify anything uncertain, conflicting, or version-specific.
Verification
python D:\dev\SKILLS\skills\skill-drafting\scripts\validate_skill_package.py D:\dev\SKILLS\skills\discord-developers
Gives 0 of the 12 instructions most apis services skills give
Counted across 424 of the 426 authors here whose files we hold, read 2026-08-06
- use plural nouns for resource namesin 41 of 424, across 32 files
- use cursor-based pagination for large datasetsin 35 of 424, across 20 files
- include rate limit headers in responsesin 25 of 424, across 13 files
- Use kebab-case for multi-word resourcesin 23 of 424, across 13 files
- version APIs in the URL pathin 19 of 424, across 9 files
- use semantic HTTP status codesin 18 of 424, across 8 files
- verify webhook signaturesin 18 of 424, across 11 files
- use query parameters for filteringin 17 of 424, across 6 files
- use async database operationsin 14 of 424, across 7 files
- wrap successful responses in a data fieldin 13 of 424, across 3 files
- prefix sorting parameters with a hyphen for descending orderin 13 of 424, across 3 files
- set appropriate HTTP status codesin 13 of 424, across 6 files
Said here and by no other author read
- pick the one file matching the subject
- read only that file
- open another file only if the task spans subjects
- grep across files when needed
- treat every identifier as an exact reference fact
- consult official documentation to verify uncertainties
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.