slack-realtime-events_skill

This skill helps you build real-time Slack apps by handling messages, mentions, interactions, and commands with Socket Mode or Events API.
  • Go

3

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill linehaul-ai/linehaulai-claude-marketplace --skill slack-realtime-events

  • SKILL.md5.7 KB

Overview

This skill implements real-time Slack event handling using Socket Mode and the Events API for Go-based apps. It provides patterns for handling messages, app mentions, reactions, interactive components, slash commands, and connection management. Use it to build responsive, event-driven Slack bots and integrations that run locally, behind firewalls, or in production cloud environments.

How this skill works

The skill wires a slack-go client to either Socket Mode (WebSocket) or the Events API (HTTP webhooks). It reads incoming envelopes or HTTP requests, acknowledges events, dispatches handlers for event types (message, app_mention, reaction, etc.), and responds via the Slack Web API. It includes patterns for interactive components (buttons, modals), slash commands, graceful shutdown, and error handling.

When to use it

  • Building interactive Slack bots that must respond in real time
  • Running a Slack app on localhost or behind a firewall (use Socket Mode)
  • Deploying to production with a public HTTPS endpoint (use Events API)
  • Handling button clicks, modal submissions, reactions, or slash commands
  • Creating event-driven automations that react to workspace activity

Best practices

  • Acknowledge incoming events immediately to avoid timeouts
  • Filter out bot-generated messages to prevent loops
  • Run long-running work in goroutines to avoid blocking handlers
  • Verify Events API request signatures in HTTP handlers
  • Implement reconnection and error handling for Socket Mode clients
  • Use graceful shutdown with context cancellation to stop cleanly

Example use cases

  • A helpdesk bot that replies to app mentions and opens modals for ticket details
  • CI/CD approval workflow that uses button actions to approve or reject deployments
  • Feedback collector that opens a modal, processes submission, and stores results
  • Monitoring bot that reacts to keywords and posts status updates in channels
  • Slash-command driven utilities like /deploy or /status with immediate or delayed responses

FAQ

Choose Socket Mode when your app cannot expose a public HTTPS endpoint (local development, firewalled environments) or when you prefer a single websocket connection. Use Events API when you have a reliable public endpoint and webhook-based architecture.

How do I avoid duplicate or looping responses?

Ignore events originating from your bot (check BotID), acknowledge events promptly, and design idempotent handlers for retries or repeated deliveries.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational