discord
- Repo stars 432
- License MIT
- Author repo understudy
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- 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 explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Common Actions (Examples)
{
"action": "send",
"channel": "discord",
"recipient": "channel:123",
"text": "hello"
}
# 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_send` schema: `recipient`, `text`, `threadId`, `replyTo`, `messageId`, `emoji`, `attachmentUrl`, `attachmentType`, `attachmentName`, `attachmentMimeType`.
- Prefer explicit ids in the recipient string when possible, for example `channel:1234567890` or `user: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`, or `set-presence`.
## Targets
- Send-like actions: `recipient: "channel:<id>"` or `recipient: "user:<id>"`.
- Message-specific actions: use `messageId`, and include `recipient` when the adapter needs target context.
## Common Actions (Examples)
Send message:
```json
{
"action": "send",
"channel": "discord",
"recipient": "channel:123",
"text": "hello"
}
```
Reply to a message:
```json
{
"action": "reply",
"channel": "discord",
"recipient": "channel:123",
"replyTo": "456",
"text": "Thanks, looking now."
}
```
Send with attachment:
```json
{
"action": "sendAttachment",
"channel": "discord",
"recipient": "channel:123",
"text": "see attachment",
"attachmentUrl": "/tmp/example.png",
"attachmentType": "image",
"attachmentName": "example.png"
}
```
```json
{
"action": "edit",
"channel": "discord",
"recipient": "channel:123",
"messageId": "456",
"text": "fixed typo"
}
```
```json
{
"action": "react",
"channel": "discord",
"recipient": "channel:123",
"messageId": "456",
"emoji": "✅"
}
```
```json
{
"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>`.
Sections and files
Listed in source order.
sections -> Musts → Guidelines → Targets → Common Actions (Examples) → Writing Style (Discord)
terms -> Use the messagesend tool. · - Always: channel: "discord". · - Avoid Markdown tables in outbound Discord messages. · - Send-like actions: recipient: "channel:<id>" or recipient: "user:<id>". · - Short, conversational, low ceremony.
files/cmd -> message_send · discord · channel: "discord" · recipient · text · threadId · replyTo · messageId
body sha256 -> d7e7493ea843
Musts
Always:
channel: "discord". Use the canonicalmessage_sendschema:recipient,text,threadId,replyTo,messageId,emoji,attachmentUrl,attachmentType,attachmentName,attachmentMimeType. Prefer explicit ids in the recipient string when possible, for examplechannel: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 ascomponents,embeds,pollQuestion,thread-create,search, orset-presence.Targets
Send-like actions:
recipient: "channel:<id>"orrecipient: "user:<id>". Message-specific actions: usemessageId, and includerecipientwhen the adapter needs target context.Common Actions (Examples)
Send message: Reply to a message: Send with attachment: 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>.