Skill Detail

Slack Bolt Event Subscription Debugger

Debugs Slack app event flows with the Bolt SDK, signature verification, `app.event()` handlers, and `ack()` timing. Useful for tracing why Events API deliveries, slash commands, or interactive callbacks are failing in real integration environments.

Integrations & ConnectorsClaude Code
Integrations & Connectors Claude Code Security Reviewed
Tool match: slack ⭐ 2.9k GitHub stars ⬇ 2.5M/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill slack-bolt-event-subscription-debugger Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Last updated
Apr 2, 2026
Quick brief

Slack Bolt Event Subscription Debugger is focused on one of the most frustrating parts of Slack app development: knowing whether an event actually arrived, was verified correctly, and was acknowledged within Slack’s deadline. The skill works with core Bolt concepts such as app.event(), app.command(), ack(), and signature verification based on the Slack signing secret. It is equally useful for classic Events API subscriptions, slash commands, and interactive payloads from buttons or modals.

How it works

What this skill actually does

The workflow helps isolate common failure modes, including slow acknowledgements, malformed request bodies, mismatched routes, and middleware that rewrites headers before Bolt sees them. That matters because many Slack integration bugs look like β€œnothing happened” when the real problem is a failed verification step or a handler that never reached ack() in time. This skill pushes those issues into the open.

Use it when building or maintaining Slack integrations that need dependable event handling, better diagnostic visibility, and a cleaner path from incoming callbacks to business logic.