discord

Send messages to Discord channels and users via a generic message tool.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/191854169/openclawFork --skill discord-191854169
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discord
Source: https://github.com/191854169/openclawFork/tree/main/skills/discord
Command: npx skills add https://github.com/191854169/openclawFork --skill discord-191854169

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Discord Skill enables rapid, policy-conscious messaging to Discord channels or users via a unified message tool, avoiding provider-specific bindings.

Core Features & Use Cases

  • Send messages to Discord channels or users using a single, generic message interface.
  • Enforces gating rules under channels.discord.actions.* and requires explicit IDs (guildId, channelId, messageId, userId) for precise control.
  • Supports multi-account scenarios via optional accountId for workflows that span multiple guilds or desks.

Quick Start

Tell the agent to send a test message to a Discord channel using the message tool.

Frequently Asked Questions about discord

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

FAQPage Schema
How do I send a message to a Discord channel using a generic message tool?▼

To send Discord messages, you use a provider-agnostic message tool by specifying the channel parameter as discord and providing explicit IDs like guildId and channelId for precise targeting.

Can I target specific Discord users or channels with explicit IDs?▼

Yes, Discord messaging requires explicit IDs such as guildId, channelId, messageId, and userId to ensure precise control over whether the message reaches a channel or a direct message recipient.

How do I manage Discord messaging permissions across multiple accounts?▼

Discord multi-account messaging is managed via an optional accountId parameter, while gating rules under channels.discord.actions.* enforce specific permissions and policy compliance for each action.

Does the Discord message tool require a provider-specific binding?▼

No, the Discord message tool uses a provider-agnostic interface, avoiding provider-specific bindings while still requiring explicit channel and user IDs to route messages accurately.

What are the limitations of using generic messaging for Discord automation?▼

Limitations include the strict enforcement of gating rules under channels.discord.actions.* and the requirement to provide explicit guildId, channelId, or userId values for every message sent.

Why are gating rules enforced for Discord channel messages?▼

Gating rules under channels.discord.actions.* are enforced during Discord messaging to maintain policy-conscious control, ensuring automated messages comply with predefined channel permissions.