discord

The Discord integration enables AI agents to interact directly within Discord environments, facilitating communication, moderation, and automated task management. Designed for personal assistants and power users, it streamlines server interactions by wrapping standard Discord API functionalities into a unified interface. By abstracting the complexity of Discord's proprietary API, this skill allows agents to participate in conversations, manage server activity, and execute administrative commands with minimal overhead.

• Support for real-time messaging, including text delivery, media attachment handling, and optional silent notification modes for discreet operation.
• Rich UI capabilities using Carbon v2 components, enabling agents to render structured data, buttons, and interactive elements directly in Discord threads or channels.
• Advanced interaction features including reactions, message editing, thread creation, channel polling, and content pinning to support complex workflows.
• Administrative and moderation hooks that allow agents to manage server presence, search message history, and perform role-based actions according to established security gating.
• Native support for user mentions using standard Discord protocols and efficient message routing via channel or user IDs.

Usage notes and best practices:

• Ensure the agent is properly gated under the configured channels.discord.actions path to maintain strict moderation and security control over sensitive server settings.
• Prioritize the use of Carbon v2 components for rich user interfaces; legacy embed structures are supported but should be reserved for compatibility-critical environments.
• When building automation workflows, use explicit IDs for guilds, channels, and users to ensure high-fidelity message delivery and reliable state tracking across sessions.
• Avoid using markdown tables in outbound messages as they are not natively rendered by the Discord client in a readable format; prefer structured text or interactive components instead.
• For search operations, utilize the guildId and specific channelIds to limit scope and improve performance when querying large message archives.