diff --git a/.claude/skills/add-slack-v2/SKILL.md b/.claude/skills/add-slack-v2/SKILL.md
index 3d652f7..a7c8e39 100644
--- a/.claude/skills/add-slack-v2/SKILL.md
+++ b/.claude/skills/add-slack-v2/SKILL.md
@@ -43,9 +43,20 @@ npm run build
    - `chat:write`, `channels:history`, `groups:history`, `im:history`, `channels:read`, `groups:read`, `users:read`, `reactions:write`
 4. Click **Install to Workspace** and copy the **Bot User OAuth Token** (`xoxb-...`)
 5. Go to **Basic Information** and copy the **Signing Secret**
-6. Go to **Event Subscriptions**, enable events, and subscribe to:
-   - `message.channels`, `message.groups`, `message.im`, `app_mention`
-7. Set the Request URL to your webhook endpoint (e.g., `https://your-domain/webhook/slack`)
+
+### Enable DMs
+
+6. Go to **App Home** and enable the **Messages Tab**
+7. Check **"Allow users to send Slash commands and messages from the messages tab"**
+
+### Event Subscriptions
+
+8. Go to **Event Subscriptions** and toggle **Enable Events**
+9. Set the **Request URL** to `https://your-domain/api/webhooks/slack` — Slack will send a verification challenge; it must pass before you can save
+10. Under **Subscribe to bot events**, add:
+    - `message.channels`, `message.groups`, `message.im`, `app_mention`
+11. Click **Save Changes**
+12. Slack will show a banner asking you to **reinstall the app** — click it to apply the new event subscriptions
 
 ### Configure environment
 
@@ -58,6 +69,10 @@ SLACK_SIGNING_SECRET=your-signing-secret
 
 Sync to container: `mkdir -p data/env && cp .env data/env/env`
 
+### Webhook server
+
+The Chat SDK bridge automatically starts a shared webhook server on port 3000 (configurable via `WEBHOOK_PORT` env var). The server handles `/api/webhooks/slack` for Slack and other webhook-based adapters. This port must be publicly reachable from the internet for Slack to deliver events.
+
 ## Next Steps
 
 If you're in the middle of `/setup`, return to the setup flow now.
@@ -68,7 +83,8 @@ Otherwise, run `/manage-channels` to wire this channel to an agent group.
 
 - **type**: `slack`
 - **terminology**: Slack has "workspaces" containing "channels." Channels can be public (#general) or private. The bot can also receive direct messages.
-- **how-to-find-id**: Right-click a channel name > "View channel details" — the Channel ID is at the bottom (starts with C). Or copy the channel link — the ID is the last segment of the URL.
+- **platform-id-format**: `slack:{channelId}` for channels (e.g., `slack:C0123ABC`), `slack:{dmId}` for DMs (e.g., `slack:D0ARWEBLV63`)
+- **how-to-find-id**: Right-click a channel name > "View channel details" — the Channel ID is at the bottom (starts with C). For DMs, the ID starts with D. Or copy the channel link — the ID is the last segment of the URL.
 - **supports-threads**: yes
 - **typical-use**: Interactive chat — team channels or direct messages
 - **default-isolation**: Same agent group for channels where you're the primary user. Separate agent group for channels with different teams or sensitive contexts.