Discord — bot API access for agents

This skill gives an agent a presence on Discord through an official bot application: see which servers the bot is in, list channels, read recent messages, post, and react — all plain REST against https://discord.com/api/v10. This is the only sanctioned route; automating a personal user account (a "self-bot") violates Discord's Terms of Service and gets the account banned.

Setup is deliberate: create an application in the Discord Developer Portal, add a Bot, store the token in a local file with mode 0600 (read at runtime, never committed, logged, or pasted into chat), and enable only the privileged gateway intents you need. A server admin must open the bot's OAuth2 invite URL and pick the server — bots cannot join servers on their own or accept normal invite links.

The tooling section maps each job to its endpoint — identity, guild list, channel list, message history, post, react (with URL-encoded emoji) — plus how to build the invite URL with a sensible permissions bitfield (3072 = View Channel + Send Messages as a read/post minimum).

Operating rules cover the failure modes: a 401 means the token is wrong or revoked, while a 403 usually means the bot lacks a permission in that server — check permissions before blaming the token. On HTTP 429, wait the retry_after value instead of retrying immediately, disclose the bot as a bot where it interacts with people, and follow each server's own posting rules.