Files
nanoclaw/.claude/skills/add-slack-v2/SKILL.md
meeech 211d2b5877 docs: convert all skill instructions from npm to pnpm
Batch update 62 files across .claude/skills/ — SKILL.md, REMOVE.md,
and script files. Conversions: npm run -> pnpm run, npm install ->
pnpm install, npx -> pnpm exec/dlx, npm uninstall -> pnpm uninstall,
package-lock.json -> pnpm-lock.yaml, shebangs updated.
2026-04-17 09:22:45 +03:00

3.4 KiB

name, description
name description
add-slack-v2 Add Slack channel integration to NanoClaw v2 via Chat SDK.

Add Slack Channel

Adds Slack support to NanoClaw v2 using the Chat SDK bridge.

Pre-flight

Check if src/channels/slack.ts exists and the import is uncommented in src/channels/index.ts. If both are in place, skip to Credentials.

Install

Install the adapter package

pnpm install @chat-adapter/slack

Enable the channel

Uncomment the Slack import in src/channels/index.ts:

import './slack.js';

Build

pnpm run build

Credentials

Create Slack App

  1. Go to api.slack.com/apps and click Create New App > From scratch
  2. Name it (e.g., "NanoClaw") and select your workspace
  3. Go to OAuth & Permissions and add Bot Token Scopes:
    • 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

Enable DMs

  1. Go to App Home and enable the Messages Tab
  2. Check "Allow users to send Slash commands and messages from the messages tab"

Event Subscriptions

  1. Go to Event Subscriptions and toggle Enable Events
  2. Set the Request URL to https://your-domain/webhook/slack — Slack will send a verification challenge; it must pass before you can save
  3. Under Subscribe to bot events, add:
    • message.channels, message.groups, message.im, app_mention
  4. Click Save Changes
  5. Slack will show a banner asking you to reinstall the app — click it to apply the new event subscriptions

Configure environment

Add to .env:

SLACK_BOT_TOKEN=xoxb-your-bot-token
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 /webhook/slack for Slack and other webhook-based adapters. This port must be publicly reachable from the internet for Slack to deliver events.

If running locally, discuss options for exposing the server — e.g. ngrok (ngrok http 3000), Cloudflare Tunnel, or a reverse proxy on a VPS. The resulting public URL becomes the base for https://your-domain/webhook/slack.

Next Steps

If you're in the middle of /setup, return to the setup flow now.

Otherwise, run /manage-channels to wire this channel to an agent group.

Channel Info

  • type: slack
  • terminology: Slack has "workspaces" containing "channels." Channels can be public (#general) or private. The bot can also receive direct messages.
  • 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.