agentleFS
jalbarrangjalbarrang/skills/discord/SKILL.md

discord

Skill2 starsChanged 3 months agoMITView on GitHub

Read Discord guild channels and message history, and download message attachments via the Discord bot REST API (v10). Use when the user asks to read Discord channels or messages, list guild text channels, download a Discord attachment or image, work with guild/channel/message snowflake IDs, or mentions DISCORD_BOT_TOKEN.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, voice-call and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • seedprodSkill

    voice-call

    Start voice calls via the OpenClaw voice-call plugin.

    Also in 17 projects that use this

  • seedprodSkill

    session-logs

    Search and analyze your own session logs (older/parent conversations) using jq.

    Also in 17 projects that use this

  • hkyutongSkill

    openclaw-release-maintainer

    Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

    Also in 4 projects that use this

  • AtomicBot-aiSkill

    taskflow

    Also in 6 projects that use this

  • +7 more from seedprod

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a bot at Discord Developer Portal → Bot → Reset Token.

    line 12
  2. Very specific:

    Run from any cwd as node <skill-dir>/scripts/<name>.mjs ….

    line 32
  3. Very specific:

    Read with read.mjs; messages print oldest-first with author, timestamp, reactions, and 📎 attachment URLs.

    line 45
  4. Very specific:

    When a message shows 📎 name (https://cdn.discordapp.com/…), download with download.mjs <url>, then read the printed path for images.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “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

Self-contained Discord bot REST skill. Scripts use Node ≥20 fetch only — no npm dependencies. Bot-token READS only (no user automation, no message sends).

Setup

  1. Create a bot at Discord Developer Portal → Bot → Reset Token.
  2. Export the token (secrets stay in the environment, never in JSON config):
export DISCORD_BOT_TOKEN=...
  1. Invite the bot with View Channel and Read Message History. It only sees guilds it has joined and channels those permissions allow.
  2. Enable Developer Mode (User Settings → Advanced) to copy guild/channel/message snowflake IDs (right-click → Copy ID).
  3. Optional non-secret defaults in .agents/discord.json (project) or ~/.agents/discord.json:
{
  "defaultGuild": "123456789012345678",
  "messageLimit": 50
}

Scripts

Run from any cwd as node <skill-dir>/scripts/<name>.mjs ….

ScriptUsage
channels.mjsnode scripts/channels.mjs [--guild <id>]
read.mjsnode scripts/read.mjs <channel> [--limit N] [--before <msgId>] [--after <msgId>]
download.mjsnode scripts/download.mjs <attachment-url>

Deep docs: reference/channels.md, reference/messages.md, reference/attachments.md.

Workflow

  1. List channels with channels.mjs (pass --guild or set defaultGuild).
  2. Read with read.mjs; messages print oldest-first with author, timestamp, reactions, and 📎 attachment URLs.
  3. When a message shows 📎 name (https://cdn.discordapp.com/…), download with download.mjs <url>, then read the printed path for images.

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.