agentleFS
DingyangLyuDingyangLyu/MatClaw/.claude/skills/add-discord/SKILL.md

add-discord

Skill98 starsChanged 8 months agoApache-2.0View on GitHub

This skill adds Discord support to MatClaw using the skills engine for deterministic code changes, then walks through interactive setup. Read .matclaw/state.yaml. If discord is in applied_skills, skip to Phase 3 (Setup). The code changes are already in place. Use AskUserQuestion to collect configuration: AskUserQuestion: Do you have a Discord bot token, or do you need to create one? If they have one, collect it now. If not, we'll create one in Phase 3. Run the skills engine to apply…

  • Reads credentials

10 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-anydoc, add-clidash 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.
  • TomGranotSkill

    add-anydoc

    Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.

    Also in 5 projects that use this

  • TomGranotSkill

    add-clidash

    Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.

    Also in 5 projects that use this

  • b1rdmaniaSkill

    migrate-memory

    Migrate from monolith CLAUDE.md to the three-file memory system (identity + state + log). Non-destructive — backs up the original first.

    Also in 7 projects that use this

  • qwibitaiSkill

    add-iron-proxy

    Install or refresh Iron Proxy and its official Iron Control web console for NanoClaw. Use when selecting the Iron gateway, adding its management UI, configuring credentials and grants, or restoring the proxy, approval bridge, and agent guidance.

    Also in 4 projects that use this

  • qwibitaiSkill

    add-mattermost

    Add a self-hosted or cloud Mattermost bot channel through the Chat SDK bridge, reusing a healthy server when available and linking to official server setup guidance when needed.

    Also in 4 projects that use this

  • nanocoaiSkill

    add-cursor

    Use Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).

    Also in 3 projects that use this

  • +5 more from TomGranot
  • +1 more from qwibitai

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 10 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

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

    Read .matclaw/state.yaml. If discord is in applied_skills, skip to Phase 3 (Setup).

    line 9
  2. Very specific:

    Use AskUserQuestion to collect configuration:

    line 13
  3. Distinctive:

    If they have one, collect it now.

    line 17
  4. Very specific:

    Run the skills engine to apply this skill's code package.

    line 21
  5. Very specific:

    If .matclaw/ directory doesn't exist yet:

    line 25
  6. Distinctive:

    If the apply reports merge conflicts, read the intent file:

    line 46
  7. Distinctive:

    All tests must pass (including the new Discord tests) and build must be clean before proceeding.

    line 56
  8. Distinctive:

    If the user doesn't have a bot token, tell them:

    line 62
  9. Distinctive:

    Wait for the user to provide the token.

    line 78
  10. Very specific:

    Wait for the user to provide the channel ID (format: dc:1234567890123456).

    line 119
  11. Distinctive:

    Use the IPC register flow or register directly.

    line 123
  12. Very specific:

    Check DISCORD_BOT_TOKEN is set in .env AND synced to data/env/env

    line 172
  13. Very specific:

    Check channel is registered: sqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE 'dc:%'"

    line 173
  14. Distinctive:

    Verify the bot has been invited to the server (check OAuth2 URL was used)

    line 176
  15. Very specific:

    Update the registered group's requiresTrigger to false

    line 181
  16. Distinctive:

    If the bot connects but can't read messages, ensure:

    line 186
  17. Distinctive:

    If you can't copy the channel ID:

    line 194
  18. Distinctive:

    Ensure Developer Mode is enabled: User Settings > Advanced > Developer Mode

    line 195

“Common” is measured: kept by at least 6 in 10 of the 10 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

Add Discord Channel

This skill adds Discord support to MatClaw using the skills engine for deterministic code changes, then walks through interactive setup.

Phase 1: Pre-flight

Check if already applied

Read .matclaw/state.yaml. If discord is in applied_skills, skip to Phase 3 (Setup). The code changes are already in place.

Ask the user

Use AskUserQuestion to collect configuration:

AskUserQuestion: Do you have a Discord bot token, or do you need to create one?

If they have one, collect it now. If not, we'll create one in Phase 3.

Phase 2: Apply Code Changes

Run the skills engine to apply this skill's code package. The package files are in this directory alongside this SKILL.md.

Initialize skills system (if needed)

If .matclaw/ directory doesn't exist yet:

npx tsx scripts/apply-skill.ts --init

Or call initSkillsSystem() from skills-engine/migrate.ts.

Apply the skill

npx tsx scripts/apply-skill.ts .claude/skills/add-discord

This deterministically:

  • Adds src/channels/discord.ts (DiscordChannel class with self-registration via registerChannel)
  • Adds src/channels/discord.test.ts (unit tests with discord.js mock)
  • Appends import './discord.js' to the channel barrel file src/channels/index.ts
  • Installs the discord.js npm dependency
  • Records the application in .matclaw/state.yaml

If the apply reports merge conflicts, read the intent file:

  • modify/src/channels/index.ts.intent.md — what changed and invariants

Validate code changes

npm test
npm run build

All tests must pass (including the new Discord tests) and build must be clean before proceeding.

Phase 3: Setup

Create Discord Bot (if needed)

If the user doesn't have a bot token, tell them:

I need you to create a Discord bot:

  1. Go to the Discord Developer Portal
  2. Click New Application and give it a name (e.g., "Andy Assistant")
  3. Go to the Bot tab on the left sidebar
  4. Click Reset Token to generate a new bot token — copy it immediately (you can only see it once)
  5. Under Privileged Gateway Intents, enable:
    • Message Content Intent (required to read message text)
    • Server Members Intent (optional, for member display names)
  6. Go to OAuth2 > URL Generator:
    • Scopes: select bot
    • Bot Permissions: select Send Messages, Read Message History, View Channels
    • Copy the generated URL and open it in your browser to invite the bot to your server

Wait for the user to provide the token.

Configure environment

Add to .env:

DISCORD_BOT_TOKEN=<their-token>

Channels auto-enable when their credentials are present — no extra configuration needed.

Sync to container environment:

mkdir -p data/env && cp .env data/env/env

The container reads environment from data/env/env, not .env directly.

Build and restart

npm run build
launchctl kickstart -k gui/$(id -u)/com.matclaw

Phase 4: Registration

Get Channel ID

Tell the user:

To get the channel ID for registration:

  1. In Discord, go to User Settings > Advanced > Enable Developer Mode
  2. Right-click the text channel you want the bot to respond in
  3. Click Copy Channel ID

The channel ID will be a long number like 1234567890123456.

Wait for the user to provide the channel ID (format: dc:1234567890123456).

Register the channel

Use the IPC register flow or register directly. The channel ID, name, and folder name are needed.

For a main channel (responds to all messages):

registerGroup("dc:<channel-id>", {
  name: "<server-name> #<channel-name>",
  folder: "discord_main",
  trigger: `@${ASSISTANT_NAME}`,
  added_at: new Date().toISOString(),
  requiresTrigger: false,
  isMain: true,
});

For additional channels (trigger-only):

registerGroup("dc:<channel-id>", {
  name: "<server-name> #<channel-name>",
  folder: "discord_<channel-name>",
  trigger: `@${ASSISTANT_NAME}`,
  added_at: new Date().toISOString(),
  requiresTrigger: true,
});

Phase 5: Verify

Test the connection

Tell the user:

Send a message in your registered Discord channel:

  • For main channel: Any message works
  • For non-main: @mention the bot in Discord

The bot should respond within a few seconds.

Check logs if needed

tail -f logs/matclaw.log

Troubleshooting

Bot not responding

  1. Check DISCORD_BOT_TOKEN is set in .env AND synced to data/env/env
  2. Check channel is registered: sqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE 'dc:%'"
  3. For non-main channels: message must include trigger pattern (@mention the bot)
  4. Service is running: launchctl list | grep matclaw
  5. Verify the bot has been invited to the server (check OAuth2 URL was used)

Bot only responds to @mentions

This is the default behavior for non-main channels (requiresTrigger: true). To change:

  • Update the registered group's requiresTrigger to false
  • Or register the channel as the main channel

Message Content Intent not enabled

If the bot connects but can't read messages, ensure:

  1. Go to Discord Developer Portal
  2. Select your application > Bot tab
  3. Under Privileged Gateway Intents, enable Message Content Intent
  4. Restart MatClaw

Getting Channel ID

If you can't copy the channel ID:

  • Ensure Developer Mode is enabled: User Settings > Advanced > Developer Mode
  • Right-click the channel name in the server sidebar > Copy Channel ID

After Setup

The Discord bot supports:

  • Text messages in registered channels
  • Attachment descriptions (images, videos, files shown as placeholders)
  • Reply context (shows who the user is replying to)
  • @mention translation (Discord <@botId> → MatClaw trigger format)
  • Message splitting for responses over 2000 characters
  • Typing indicators while the agent processes

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.