Skip to main content
Agent skill

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Discord Clawd when an AI agent needs a reusable SKILL.md workflow for this job: Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

When not to use it

Skip Discord Clawd when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/discord-clawd
# Save SKILL.md to ~/.claude/skills/discord-clawd/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/discord-clawd/SKILL.md. For a shared project, commit the folder at .claude/skills/discord-clawd/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Discord Clawd skill for this task: Use Discord Clawd when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

67/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
67/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Discord Clawd

Use this when the task is to talk with the Discord-backed agent/session, ask it a question, or post through that route.

For Discord archive/history/search, use `$discrawl` instead.

## Transport

Use the OpenClaw relay helper:

```bash cd ~/Projects/agent-scripts python3 skills/openclaw-relay/scripts/openclaw_relay.py targets python3 skills/openclaw-relay/scripts/openclaw_relay.py resolve --target maintainers ```

If the target alias exists, prefer a private ask first:

```bash python3 skills/openclaw-relay/scripts/openclaw_relay.py ask \ --target maintainers \ --message "Reply with exactly OK." ```

Use `publish` when the session should decide whether to post. Use `force-send` only when the user explicitly wants a message posted.

## Guardrails

- Resolve the target before sending real content. - Report the target and delivery mode used. - Do not use this for local Discord archive queries. - Do not expose gateway tokens or session secrets.

Intended uses

  • Use Discord Clawd when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.