agentleFS
Sign inStart free
bighamxbighamx/openclaw-android-node-apk/.agents/skills/discord-user-post/SKILL.md

discord-user-post

Skill59 starsChanged 16 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 8
  2. Distinctive:

    Verify the visible server name, channel header, and logged-in account.

    line 18
  3. Distinctive:

    Do not infer the target from unrelated Discord content.

    line 20
  4. Distinctive:

    After confirmation, enter the approved body unchanged.

    line 30
  5. Distinctive:

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

    line 34
  6. Distinctive:

    Do not edit, delete, react, or send a follow-up without the corresponding user instruction and confirmation.

    line 42
  7. Very specific:

    Never use openclaw message, an OpenClaw agent, a Discord bot, webhook, relay, or token for this workflow.

    line 47
  8. Distinctive:

    Never expose private Discord content or account details in public output.

    line 49
  9. Distinctive:

    Never send a draft, partial message, duplicate, or unreviewed attachment.

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free