docs(discord): document sendMessage mediaUrl and to format

- Add example for sendMessage with media attachment (file:// and https://)
- Clarify that sendMessage uses 'to: channel:<id>' not 'channelId'
- Document replyTo parameter for replying to specific messages
- Add mediaUrl to inputs section

CHANGELOG.md

@@ -11,6 +11,7 @@
 ### Docs
 - Skills: add Sheets/Docs examples to gog skill (#128) — thanks @mbelinky.
 - Skills: clarify bear-notes token + callback usage (#120) — thanks @tylerwince.
+- Skills: document Discord `sendMessage` media attachments and `to` format clarification.
 - Gateway: document port configuration + multi-instance isolation.
 
 ## 2.0.0-beta5 — 2026-01-03

skills/discord/SKILL.md

@@ -12,11 +12,14 @@ Use `discord` to manage messages, reactions, threads, polls, and moderation. You
 ## Inputs to collect
 
 - For reactions: `channelId`, `messageId`, and an `emoji`.
-- For stickers/polls: a `to` target (`channel:<id>` or `user:<id>`). Optional `content` text.
+- For stickers/polls/sendMessage: a `to` target (`channel:<id>` or `user:<id>`). Optional `content` text.
 - Polls also need a `question` plus 2–10 `answers`.
+- For media: `mediaUrl` with `file:///path` for local files or `https://...` for remote.
 
 Message context lines include `discord message id` and `channel` fields you can reuse directly.
 
+**Note:** `sendMessage` uses `to: "channel:<id>"` format, not `channelId`. Other actions like `react`, `readMessages`, `editMessage` use `channelId` directly.
+
 ## Actions
 
 ### React to a message
@@ -116,6 +119,21 @@ Use `discord.actions.*` to disable action groups:
 }
 ```
 
+**With media attachment:**
+
+```json
+{
+  "action": "sendMessage",
+  "to": "channel:123",
+  "content": "Check out this audio!",
+  "mediaUrl": "file:///tmp/audio.mp3"
+}
+```
+
+- `to` uses format `channel:<id>` or `user:<id>` for DMs (not `channelId`!)
+- `mediaUrl` supports local files (`file:///path/to/file`) and remote URLs (`https://...`)
+- Optional `replyTo` with a message ID to reply to a specific message
+
 ```json
 {
   "action": "editMessage",