discord
- Repo stars 432
- License MIT
- Author updated Live
- Author repo understudy
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @understudy-ai · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: discord
description: Discord messaging via `message_send` (channel=discord). Use for outbound sends, replies, edits…
category: other
runtime: no special runtime
---
# discord output preview
## PART A: Task fit
- Use case: Discord messaging via `message_send` (channel=discord). Use for outbound sends, replies, edits, reactions, deletes, and attachment sends on Discord. Use the message_send tool. Understudy does not expose a separate provider-specific discord tool. makes outbound network calls. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Musts / Guidelines / Targets” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Discord messaging via `message_send` (channel=discord). Use for outbound sends, replies, edits, reactions, deletes, and attachment sends on Discord. Use the message_send tool. Understudy does not expose a separate provider-specific discord tool. makes outbound network calls. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Musts / Guidelines / Targets” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Musts / Guidelines / Targets”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: discord
description: Discord messaging via `message_send` (channel=discord). Use for outbound sends, replies, edits…
category: other
source: understudy-ai/understudy
---
# discord
## When to use
- Discord messaging via `message_send` (channel=discord). Use for outbound sends, replies, edits, reactions, deletes, an…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Musts / Guidelines / Targets” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "discord" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Musts / Guidelines / Targets
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Discord (Via message_send)
Use the message_send tool. Understudy does not expose a separate provider-specific discord tool.
Musts
- Always:
channel: "discord". - Use the canonical
message_sendschema:recipient,text,threadId,replyTo,messageId,emoji,attachmentUrl,attachmentType,attachmentName,attachmentMimeType. - Prefer explicit ids in the recipient string when possible, for example
channel:1234567890oruser:1234567890.
Guidelines
- Avoid Markdown tables in outbound Discord messages.
- Mention users as
<@USER_ID>. - Keep Discord actions within the current Understudy tool surface. Do not invent unsupported fields such as
components,embeds,pollQuestion,thread-create,search, orset-presence.
Targets
- Send-like actions:
recipient: "channel:<id>"orrecipient: "user:<id>". - Message-specific actions: use
messageId, and includerecipientwhen the adapter needs target context.
Common Actions (Examples)
Send message:
{
"action": "send",
"channel": "discord",
"recipient": "channel:123",
"text": "hello"
}Reply to a message:
{
"action": "reply",
"channel": "discord",
"recipient": "channel:123",
"replyTo": "456",
"text": "Thanks, looking now."
}Send with attachment:
{
"action": "sendAttachment",
"channel": "discord",
"recipient": "channel:123",
"text": "see attachment",
"attachmentUrl": "/tmp/example.png",
"attachmentType": "image",
"attachmentName": "example.png"
}{
"action": "edit",
"channel": "discord",
"recipient": "channel:123",
"messageId": "456",
"text": "fixed typo"
}{
"action": "react",
"channel": "discord",
"recipient": "channel:123",
"messageId": "456",
"emoji": "✅"
}{
"action": "delete",
"channel": "discord",
"recipient": "channel:123",
"messageId": "456"
}If you need polls, search, thread creation, pins, moderation, or presence changes, tell the user the current Understudy tool surface does not expose those Discord-specific operations directly.
Writing Style (Discord)
- Short, conversational, low ceremony.
- No markdown tables.
- Mention users as
<@USER_ID>.
Decide Fit First
message_send(channel=discord). Use for outbound sends, replies, edits, reactions, deletes, and attachme…Design Intent
How To Use It
Boundaries And Review