Files

gavrielc 00fb1bee4a chore(skills): rename add-*-v2 → add-* and drop dead v1 channel skills

Renamed 13 skill folders to drop the -v2 suffix (the v2/v1 distinction
isn't load-bearing anymore — there is no v1 runtime). Deleted the four
v1 channel skills that occupied the rename target paths (add-discord,
add-slack, add-telegram, add-whatsapp); they targeted src/v1 which is
reference-only per CLAUDE.md.

Skill content still says "v2" in places — that's a follow-up commit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-17 14:38:19 +03:00

3.9 KiB

Raw Blame History

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.

Install

v2 trunk doesn't ship channels. 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

Go to api.slack.com/apps and click Create New App > From scratch
Name it (e.g., "NanoClaw") and select your workspace
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
Click Install to Workspace and copy the Bot User OAuth Token (xoxb-...)
Go to Basic Information and copy the Signing Secret

Enable DMs

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

Event Subscriptions

Go to Event Subscriptions and toggle Enable Events
Set the Request URL to https://your-domain/webhook/slack — Slack will send a verification challenge; it must pass before you can save
Under Subscribe to bot events, add:
- message.channels, message.groups, message.im, app_mention
Click Save Changes
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.

3.9 KiB Raw Blame History