add-slack

Add Slack as an operational channel for NanoClaw agents with Socket Mode.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/spyqs/nanoclaw-email-imap --skill add-slack-spyqs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-slack
Source: https://github.com/spyqs/nanoclaw-email-imap/tree/main/.claude/skills/add-slack
Command: npx skills add https://github.com/spyqs/nanoclaw-email-imap --skill add-slack-spyqs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You want your NanoClaw AI agent to receive and respond in Slack, without manually wiring Slack events, tokens, and channel registration.

Core Features & Use Cases

  • Slack integration setup: Adds Slack channel support to NanoClaw and guides you through the required configuration.
  • Token-based Socket Mode authentication: Uses a Bot Token and App-Level Token so you don’t need a public URL.
  • Channel registration & triggers: Registers main (responds to all messages) and non-main (trigger-only) channels, then verifies connectivity.

Quick Start

Tell your AI assistant: "Run the add-slack skill, create the Slack app if needed, configure SLACK_BOT_TOKEN and SLACK_APP_TOKEN, then register my channel slack_main and verify it can respond."

Frequently Asked Questions about add-slack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add Slack channels to my AI agent for receiving and responding to messages?

Adding Slack channels to an AI agent requires configuring Socket Mode with Bot and App-Level tokens, merging the Slack channel implementation, syncing environment variables, and registering channel JIDs with appropriate triggers for message routing.

Do I need a public URL to set up Slack Socket Mode for my bot?

No, Slack Socket Mode does not require a public URL. By using a Bot Token and App-Level Token for authentication, your agent can receive Slack events and send replies without exposing a public endpoint.

What is the difference between main broadcast channels and trigger-only channels in Slack bot registration?

Main broadcast channels respond to all messages received, while non-main trigger-only channels activate solely for event-driven conversations based on specific triggers defined during the channel registration process.

What steps are involved in configuring a Slack bot token environment for an agent integration?

Configuring a Slack bot token environment involves collecting the Bot Token and App-Level Token, syncing them into the data/env environment template, and running a preflight check to merge existing Slack code before registering channels.

Can I register multiple Slack channels with different triggers for my agent?

Yes, you can register multiple Slack channels. The process supports registering both main broadcast channels that respond to all messages and non-main channels that operate as trigger-only for specific event-driven conversations.

Why does my Slack integration require a preflight check before adding channel support?

A preflight check is required to detect existing Slack code within your project before merging the new Slack channel implementation, preventing code conflicts and ensuring a clean integration of tests and environment templates.