discord-user-post

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# 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 `quiet-core-bot message`, an Quiet Core bot 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.

From liuda1999/Quiet-Core-bot, MIT.

More from liuda1999/Quiet-Core-bot