add-discord
b1rdmania/ghostclaw/.claude/skills/add-discord/SKILL.md
This skill adds Discord support to GhostClaw using the skills engine for deterministic code changes, then walks through interactive setup. Read .ghostclaw/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: Should Discord replace WhatsApp or run alongside it? - Replace WhatsApp - Discord will be the only channel (sets DISCORD_ONLY=true) - Alongside - Both Discord and WhatsApp channels active AskUserQuestion: Do you have a Discord…
- Reads credentials
What's in it
- Add Discord Channel
- Phase 1: Pre-flight
- Check if already applied
- Ask the user
- Phase 2: Apply Code Changes
- Initialize skills system (if needed)
- Apply the skill
- Validate code changes
- Phase 3: Setup
- Create Discord Bot (if needed)
- Configure environment
- Build and restart
- Phase 4: Registration
- Get Channel ID
- Register the channel
- Phase 5: Verify
- Test the connection
- Check logs if needed
- Troubleshooting
- Bot not responding
- Bot only responds to @mentions
- Message Content Intent not enabled
- Getting Channel ID
- After Setup
# Add Discord Channel
This skill adds Discord support to GhostClaw using the skills engine for deterministic code changes, then walks through interactive setup.
## Phase 1: Pre-flight
### Check if already applied
Read `.ghostclaw/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: Should Discord replace WhatsApp or run alongside it?
- **Replace WhatsApp** - Discord will be the only channel (sets DISCORD_ONLY=true)
- **Alongside** - Both Discord and WhatsApp channels active
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 `.ghostclaw/` directory doesn't exist yet:
```bash
npx tsx scripts/apply-skill.ts --init
```
Or call `initSkillsSystem()` from `skills-engine/migrate.ts`.
### Apply the skill
```bash
npx tsx scripts/apply-skill.ts .claude/skills/add-discord
```
This deterministically:
- Adds `src/channels/discord.ts` (DiscordChannel class implementing Channel interface)
- Adds `src/channels/discord.test.ts` (unit tests with discord.js mock)
- Three-way merges Discord support into `src/index.ts` (multi-channel support, findChannel routing)
- Three-way merges Discord config into `src/config.ts` (DISCORD_BOT_TOKEN, DISCORD_ONLY exports)
- Three-way merges updated routing tests into `src/routing.test.ts`
- Installs the `discord.js` npm dependency
- Updates `.env.example` with `DISCORD_BOT_TOKEN` and `DISCORD_ONLY`
- Records the application in `.ghostclaw/state.yaml`
If the apply reports merge conflicts, read the intent files:
- `modify/src/index.ts.intent.md` — what changed and invariants for index.ts
- `modify/src/config.ts.intent.md` — what changed for config.ts
### Validate code changes
```bash
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](https://discord.com/developers/applications)
> 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`:
```bash
DISCORD_BOT_TOKEN=<their-token>
```
If they chose to replace WhatsApp:
```bash
DISCORD_ONLY=true
```
Sync to container environment:
```bash
cp .env data/env/env
```
The container reads environment from `data/env/env`, not `.env` directly.
### Build and restart
```bash
npm run build
launchctl kickstart -k gui/$(id -u)/com.ghostclaw
```
## 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, uses the `main` folder):
```typescript
registerGroup("dc:<channel-id>", {
name: "<server-name> #<channel-name>",
folder: "main",
trigger: `@${ASSISTANT_NAME}`,
added_at: new Date().toISOString(),
requiresTrigger: false,
});
```
For additional channels (trigger-only):
```typescript
registerGroup("dc:<channel-id>", {
name: "<server-name> #<channel-name>",
folder: "<folder-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
```bash
tail -f logs/ghostclaw.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 ghostclaw`
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](https://discord.com/developers/applications)
2. Select your application > **Bot** tab
3. Under **Privileged Gateway Intents**, enable **Message Content Intent**
4. Restart GhostClaw
### 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>` → GhostClaw trigger format)
- Message splitting for responses over 2000 characters
- Typing indicators while the agent processes
More agent context in b1rdmania/ghostclaw
55 other files this repository gives its agents.
Skill
- ab-test-setup.claude/skills/ab-test-setup/SKILL.md
- ad-creative.claude/skills/ad-creative/SKILL.md
- add-gmail-agent.claude/skills/add-gmail-agent/SKILL.md
- add-heartbeat.claude/skills/add-heartbeat/SKILL.md
- add-morning-briefing.claude/skills/add-morning-briefing/SKILL.md
- add-slack.claude/skills/add-slack/SKILL.md
- add-telegram.claude/skills/add-telegram/SKILL.md
- add-telegram-swarm.claude/skills/add-telegram-swarm/SKILL.md
- add-update-check.claude/skills/add-update-check/SKILL.md
- add-voice-reply.claude/skills/add-voice-reply/SKILL.md
- add-voice-transcription.claude/skills/add-voice-transcription/SKILL.md
- ai-seo.claude/skills/ai-seo/SKILL.md
- analytics-tracking.claude/skills/analytics-tracking/SKILL.md
- churn-prevention.claude/skills/churn-prevention/SKILL.md
- cold-email.claude/skills/cold-email/SKILL.md
- competitor-alternatives.claude/skills/competitor-alternatives/SKILL.md
- content-strategy.claude/skills/content-strategy/SKILL.md
- copy-editing.claude/skills/copy-editing/SKILL.md
- copywriting.claude/skills/copywriting/SKILL.md
- customize.claude/skills/customize/SKILL.md
- debug.claude/skills/debug/SKILL.md
- design.claude/skills/design/SKILL.md
- domain-check.claude/skills/domain-check/skill.md
- email-sequence.claude/skills/email-sequence/SKILL.md
- form-cro.claude/skills/form-cro/SKILL.md
- free-tool-strategy.claude/skills/free-tool-strategy/SKILL.md
- get-qodo-rules.claude/skills/get-qodo-rules/SKILL.md
- launch-strategy.claude/skills/launch-strategy/SKILL.md
- marketing-ideas.claude/skills/marketing-ideas/SKILL.md
- marketing-psychology.claude/skills/marketing-psychology/SKILL.md
- migrate-memory.claude/skills/migrate-memory/SKILL.md
- onboarding-cro.claude/skills/onboarding-cro/SKILL.md
- page-cro.claude/skills/page-cro/SKILL.md
- paid-ads.claude/skills/paid-ads/SKILL.md
- paywall-upgrade-cro.claude/skills/paywall-upgrade-cro/SKILL.md
- popup-cro.claude/skills/popup-cro/SKILL.md
- pr-babysitter.claude/skills/pr-babysitter/SKILL.md
- pricing-strategy.claude/skills/pricing-strategy/SKILL.md
- product-marketing-context.claude/skills/product-marketing-context/SKILL.md
- programmatic-seo.claude/skills/programmatic-seo/SKILL.md
- qodo-pr-resolver.claude/skills/qodo-pr-resolver/SKILL.md
- referral-program.claude/skills/referral-program/SKILL.md
- revops.claude/skills/revops/SKILL.md
- run-ralph.claude/skills/run-ralph/SKILL.md
- sales-enablement.claude/skills/sales-enablement/SKILL.md
- schema-markup.claude/skills/schema-markup/SKILL.md
- seo-audit.claude/skills/seo-audit/SKILL.md
- setup-ghostclaw.claude/skills/setup-ghostclaw/SKILL.md
- setup-shared-folder.claude/skills/setup-shared-folder/SKILL.md
- setup.claude/skills/setup/SKILL.md
- signup-flow-cro.claude/skills/signup-flow-cro/SKILL.md
- site-architecture.claude/skills/site-architecture/SKILL.md
- social-content.claude/skills/social-content/SKILL.md
- update-ghostclaw.claude/skills/update-ghostclaw/SKILL.md
- update-nanoclaw.claude/skills/update-nanoclaw/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Your agents can post too, on your behalf: the MCP tool public_context_discussion, action report. How to connect one.

