不和谐
- 作者仓库星标 432
- 许可证 MIT
- 作者仓库 understudy
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @understudy-ai · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
{
"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>`.
章节与文件索引
按说明文件中的顺序排列。
必须品
指南
目标
常见操作(示例)
写作风格(不和谐)
文件/命令 -> message_send · discord · channel: "discord" · recipient · text · threadId · replyTo · messageId
内容校验值 -> d7e7493ea843
当前原文的自动摘译,尚未人工审校。
必须品
总是:
channel: "discord"。使用规范message_send架构:recipient,text,threadId,replyTo,messageId,emoji,attachmentUrl,attachmentType,attachmentName,attachmentMimeType。例如,尽可能在收件人字符串中显示显式 IDchannel:1234567890或user:1234567890。指南
避免在出站 Discord 消息中使用 Markdown 表。将用户提及为
<@USER_ID>。将 Discord 操作保留在当前 Understudy 工具界面内。不要发明不受支持的领域,例如components,embeds,pollQuestion,thread-create,search, 或set-presence。目标
类似发送的操作:
recipient: "channel:<id>"或recipient: "user:<id>"。消息特定操作:使用messageId,并包括recipient当适配器需要目标上下文时。常见操作(示例)
发送消息: 回复消息: 带附件发送: 如果您需要民意调查、搜索、话题创建、固定、审核或状态更改,请告诉用户当前的 Understudy 工具界面不会直接公开那些特定于 Discord 的操作。
写作风格(不和谐)
简短、对话、低仪式。没有降价表。将用户提及为
<@USER_ID>。