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
- nanocoai/nanoclawtheir own version, first seen Nov 15, 2026
- ss2code/nanoclaw-opsedited, first seen Oct 15, 2026
- prathish-ks/isthmustheir own version, first seen Oct 12, 2026
- gavrielc/nanoclawtheir own version, first seen Oct 8, 2026
- qwibitai/nanoclawtheir own version, first seen Oct 8, 2026
- TomGranot/groupguardtheir own version, first seen Sep 3, 2026
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.
TomGranotSkilladd-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
TomGranotSkilladd-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
b1rdmaniaSkillmigrate-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
qwibitaiSkilladd-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
qwibitaiSkilladd-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
nanocoaiSkilladd-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
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- b1rdmania/ghostclaw★ 9178% same
- microsoft/amplifier-app-nanoclaw★ 513% same
- breakcafe/picoclaw★ 195% same
- mcarmona1064-cell/clawbridge-codex★ 113% same
- ss2code/nanoclaw-ops★ 111% same
Wrote their own version · 5
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- TomGranot/groupguard★ 3same name
- prathish-ks/isthmus★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-dingtalkSkill
- add-gmailSkill
- add-ollama-toolSkill
- add-parallelSkill
- add-slackSkill
- add-telegramSkill
- add-telegram-swarmSkill
- add-vaspSkill
- add-voice-transcriptionSkill
- add-whatsappSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- qodo-pr-resolverSkill
- setupSkill
- update-matclawSkill
- use-local-whisperSkill
- x-integrationSkill
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
- Very specific: line 9
Read .matclaw/state.yaml. If discord is in applied_skills, skip to Phase 3 (Setup).
- Very specific: line 13
Use AskUserQuestion to collect configuration:
- Distinctive: line 17
If they have one, collect it now.
- Very specific: line 21
Run the skills engine to apply this skill's code package.
- Very specific: line 25
If .matclaw/ directory doesn't exist yet:
- Distinctive: line 46
If the apply reports merge conflicts, read the intent file:
- Distinctive: line 56
All tests must pass (including the new Discord tests) and build must be clean before proceeding.
- Distinctive: line 62
If the user doesn't have a bot token, tell them:
- Distinctive: line 78
Wait for the user to provide the token.
- Very specific: line 119
Wait for the user to provide the channel ID (format: dc:1234567890123456).
- Distinctive: line 123
Use the IPC register flow or register directly.
- Very specific: line 172
Check DISCORD_BOT_TOKEN is set in .env AND synced to data/env/env
- Very specific: line 173
Check channel is registered: sqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE 'dc:%'"
- Distinctive: line 176
Verify the bot has been invited to the server (check OAuth2 URL was used)
- Very specific: line 181
Update the registered group's requiresTrigger to false
- Distinctive: line 186
If the bot connects but can't read messages, ensure:
- Distinctive: line 194
If you can't copy the channel ID:
- Distinctive: line 195
Ensure Developer Mode is enabled: User Settings > Advanced > Developer Mode
“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.
Files
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 --initOr call initSkillsSystem() from skills-engine/migrate.ts.
Apply the skill
npx tsx scripts/apply-skill.ts .claude/skills/add-discordThis deterministically:
- Adds
src/channels/discord.ts(DiscordChannel class with self-registration viaregisterChannel) - Adds
src/channels/discord.test.ts(unit tests with discord.js mock) - Appends
import './discord.js'to the channel barrel filesrc/channels/index.ts - Installs the
discord.jsnpm 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 buildAll 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:
- Go to the Discord Developer Portal
- Click New Application and give it a name (e.g., "Andy Assistant")
- Go to the Bot tab on the left sidebar
- Click Reset Token to generate a new bot token — copy it immediately (you can only see it once)
- Under Privileged Gateway Intents, enable:
- Message Content Intent (required to read message text)
- Server Members Intent (optional, for member display names)
- 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/envThe container reads environment from data/env/env, not .env directly.
Build and restart
npm run build
launchctl kickstart -k gui/$(id -u)/com.matclawPhase 4: Registration
Get Channel ID
Tell the user:
To get the channel ID for registration:
- In Discord, go to User Settings > Advanced > Enable Developer Mode
- Right-click the text channel you want the bot to respond in
- 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.logTroubleshooting
Bot not responding
- Check
DISCORD_BOT_TOKENis set in.envAND synced todata/env/env - Check channel is registered:
sqlite3 store/messages.db "SELECT * FROM registered_groups WHERE jid LIKE 'dc:%'" - For non-main channels: message must include trigger pattern (@mention the bot)
- Service is running:
launchctl list | grep matclaw - 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
requiresTriggertofalse - Or register the channel as the main channel
Message Content Intent not enabled
If the bot connects but can't read messages, ensure:
- Go to Discord Developer Portal
- Select your application > Bot tab
- Under Privileged Gateway Intents, enable Message Content Intent
- 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
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
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.

