|
| 1 | +--- |
| 2 | +name: discord-user-post |
| 3 | +description: Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots, webhooks, relays, agent sessions, or archive search. |
| 4 | +--- |
| 5 | + |
| 6 | +# Discord User Post |
| 7 | + |
| 8 | +Use `$computer-use` to operate `/Applications/Discord.app` in the user's |
| 9 | +existing logged-in session. This workflow represents the user directly. |
| 10 | + |
| 11 | +## Prepare |
| 12 | + |
| 13 | +1. Draft the complete final message outside Discord. |
| 14 | +2. Confirm the intended server and channel with the user when either is |
| 15 | + ambiguous. |
| 16 | +3. Open Discord and navigate to the exact destination without entering the |
| 17 | + message. |
| 18 | +4. Verify the visible server name, channel header, and logged-in account. |
| 19 | + |
| 20 | +Do not infer the target from unrelated Discord content. Stop if Discord is not |
| 21 | +logged in, the account is wrong, or the exact destination cannot be verified. |
| 22 | + |
| 23 | +## Confirm and Post |
| 24 | + |
| 25 | +Posting is representational communication. Follow the `$computer-use` |
| 26 | +confirmation policy even when the user previously asked for an announcement: |
| 27 | + |
| 28 | +1. Show the user the exact final body and verified destination. |
| 29 | +2. Request action-time confirmation before typing into Discord. |
| 30 | +3. After confirmation, enter the approved body unchanged. |
| 31 | +4. Visually inspect the composed message and destination again. |
| 32 | +5. Send once. |
| 33 | + |
| 34 | +If the body or destination changes after confirmation, request confirmation |
| 35 | +again before sending. |
| 36 | + |
| 37 | +## Verify |
| 38 | + |
| 39 | +- Confirm the message appears once, from the user's account, in the intended |
| 40 | + channel. |
| 41 | +- Report the server, channel, and visible send result. |
| 42 | +- Do not edit, delete, react, or send a follow-up without the corresponding |
| 43 | + user instruction and confirmation. |
| 44 | + |
| 45 | +## Guardrails |
| 46 | + |
| 47 | +- Never use `openclaw message`, an OpenClaw agent, a Discord bot, webhook, relay, |
| 48 | + or token for this workflow. |
| 49 | +- Never expose private Discord content or account details in public output. |
| 50 | +- Never send a draft, partial message, duplicate, or unreviewed attachment. |
| 51 | +- For Discord archive/history/search, use `$discrawl` instead. |
