mcpField
D
discord-user-post

discord-user-post

github.com/openclawProductivity393.3k193 installsUpdated today
Repository

About discord-user-post

A skill for posting messages to Discord through the user's existing logged-in desktop session. It requires destination verification, approval of the exact message, and a check that the post appears once.

Key features

  1. 01Use of the logged-in Discord session
  2. 02Server and channel verification
  3. 03Review and confirmation before posting
  4. 04Post-send visibility check
  5. 05Restrictions on follow-up actions

Use cases

  1. 01Posting an approved announcement
  2. 02Sending a reviewed message to a specific channel
  3. 03Verifying that a message was posted once

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/openclaw/openclaw --skill discord-user-post

After installing, type/discord-user-postin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

Discord User Post

Use $computer-use to operate /Applications/Discord.app in the user's existing logged-in session. This workflow represents the user directly.

Prepare

  1. Draft the complete final message outside Discord.
  2. Confirm the intended server and channel with the user when either is ambiguous.
  3. Open Discord and navigate to the exact destination without entering the message.
  4. Verify the visible server name, channel header, and logged-in account.

Do not infer the target from unrelated Discord content. Stop if Discord is not logged in, the account is wrong, or the exact destination cannot be verified.

Confirm and Post

Posting is representational communication. Follow the $computer-use confirmation policy even when the user previously asked for an announcement:

  1. Show the user the exact final body and verified destination.
  2. Request action-time confirmation before typing into Discord.
  3. After confirmation, enter the approved body unchanged.
  4. Visually inspect the composed message and destination again.
  5. Send once.

If the body or destination changes after confirmation, request confirmation again before sending.

Verify

  • Confirm the message appears once, from the user's account, in the intended channel.
  • Report the server, channel, and visible send result.
  • Do not edit, delete, react, or send a follow-up without the corresponding user instruction and confirmation.

Guardrails

  • Never use openclaw message, an OpenClaw agent, a Discord bot, webhook, relay, or token for this workflow.
  • Never expose private Discord content or account details in public output.
  • Never send a draft, partial message, duplicate, or unreviewed attachment.
  • For Discord archive/history/search, use $discrawl instead.

Comments

Markdown supported