wangjunxiao/nanoclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
c37609ffc813d3c7cb68b2cfe759c4005f3104ff
nanoclaw/.claude/skills/add-slack/SKILL.md
gavrielc c37609ffc8 docs(skills): drop "v2" from skill content + src/index.ts log lines 
Cleans up the prose-level v2 references that the rename commit didn't
touch. Skills now describe themselves and the codebase without "v2"
versioning language. /add-X-v2 cross-references in setup, init-first-agent,
and manage-channels updated to /add-X.

Runtime path identifiers (data/v2.db, data/v2-sessions/, container name
nanoclaw-v2) deliberately left as-is — renaming them breaks live installs
without commensurate benefit.

Verified: pnpm run build clean, 326 host tests pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-17 14:42:55 +03:00

3.9 KiB
Raw Blame History

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

Add Slack Channel

Adds Slack support via the Chat SDK bridge.

Install

NanoClaw doesn't ship channels in trunk. This skill copies the Slack adapter in from the channels branch.

Pre-flight (idempotent)

Skip to Credentials if all of these are already in place:

  • src/channels/slack.ts exists
  • src/channels/index.ts contains import './slack.js';
  • @chat-adapter/slack is listed in package.json dependencies

Otherwise continue. Every step below is safe to re-run.

1. Fetch the channels branch

git fetch origin channels

2. Copy the adapter

git show origin/channels:src/channels/slack.ts > src/channels/slack.ts

3. Append the self-registration import

Append to src/channels/index.ts (skip if the line is already present):

import './slack.js';

4. Install the adapter package (pinned)

pnpm install @chat-adapter/slack@4.26.0

5. 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.