slack-app-stinger
Start with README.md for the workflow map and detailed references.
The Slack developer playbook for slack-app-wasp-drone. Encodes opinionated, research-backed patterns for every major Slack app surface: from first Bolt app scaffold to Marketplace submission.
Quick navigation
| Task |
Guide |
| Create a new Slack app, pick HTTP vs Socket Mode |
guides/00-setup-and-bolt.md |
| Add a slash command |
guides/01-slash-commands.md |
| Build Block Kit messages and interactive components |
guides/02-block-kit.md |
| Open / push / update modals |
guides/03-modals.md |
| Subscribe to events, verify webhooks |
guides/04-events-api.md |
| Multi-workspace OAuth install flow |
guides/05-oauth-install.md |
| Submit to App Directory / Marketplace |
guides/06-app-directory.md |
Critical directives
These are the non-negotiables. Violating any of them is the most common cause of production Slack app failures. See the relevant guide for code patterns.
Acknowledge Slack payloads within 3 seconds, then dispatch async for long-running work. Slack retries unacknowledged payloads up to 3 times and flags unreliable apps. This applies to slash commands, interactive component actions, and Events API deliveries equally. Source: research/external/2026-05-20-events-api-verification.md, research/external/2026-05-20-slash-commands-interactive.md (source-repository research, not shipped with the plugin).
Verify Slack request signatures before processing any payload. Bolt does this automatically. Custom HTTP handlers (Express, FastAPI routes) must implement HMAC-SHA256 verification manually using the app's signing secret. Source: research/external/2026-05-20-events-api-verification.md (source-repository research, not shipped with the plugin).
Never store Slack tokens in plaintext config files or committed environment variables. Bot tokens (xoxb-) and signing secrets go in an environment variable manager or secrets vault. Source: research/external/2026-05-20-bolt-sdk-setup-patterns.md (source-repository research, not shipped with the plugin).
Always validate the state parameter in OAuth callbacks. Bolt auto-generates and validates state via stateSecret. Bypassing this validation is a CSRF vulnerability that allows workspace installation hijacking. Source: research/external/2026-05-20-oauth-multi-workspace.md (source-repository research, not shipped with the plugin).
Deduplicate Events API payloads using event_id before processing. Slack delivers events at-least-once. Store the event_id (Redis SETNX, DB unique constraint) and discard duplicates. Source: research/external/2026-05-20-events-api-verification.md (source-repository research, not shipped with the plugin).
If the app will be distributed commercially at scale, use HTTP mode and plan for Marketplace submission from the start. Socket Mode apps cannot be listed in the Slack Marketplace. Apps intended for commercial distribution must go through Marketplace review (December 2024 policy update). Source: research/external/2026-05-20-socket-mode-vs-http.md, research/external/2026-05-20-dev-policy-update.md (source-repository research, not shipped with the plugin).
Never use Slack data to train LLMs. This is an explicit, absolute prohibition in the December 2024 Slack App Developer Policy update ("under any circumstances"). AI-powered Slack bots must not route user message content through LLM training pipelines. Source: research/external/2026-05-20-dev-policy-update.md (source-repository research, not shipped with the plugin).
Scope note
This stinger covers the Bolt SDK (JS, Python, Java) and the classic Slack Platform. The Deno Slack SDK and the next-generation Workflow Builder platform are distinct products with separate documentation and are out of scope here. When developers encounter both in the official docs, direct them to https://tools.slack.dev/bolt-js/ (Bolt JS) vs https://tools.slack.dev/deno-slack-sdk/ (Deno/Workflow Builder) for the right starting point.
Handoff map
- Deployment infrastructure for the Bolt app backend (Lambda, Fly.io, Render): route to
devops-wasp-drone.
- Token vault, signing secret rotation, security audit: route to
security-wasp-drone.
- Django or FastAPI backend decisions beyond Bolt integration: route to
python-wasp-drone.
- Slack Connect or Enterprise Grid administration: out of scope; direct the user to Slack's enterprise documentation.
Forged by stinger-forge from ai-tools/command-briefs/slack-app-wasp-drone-command-brief.md and research/. Part of the Wasp Nest.
1---2name: slack-app-stinger-33license: AGPL-3.0-or-later4description: "Build Slack apps with Bolt. Use for slash commands, Block Kit, modals, Events API, OAuth installs, or Marketplace submission. Read README.md for the guide map."5metadata:6 source: https://skillmd.com/skills/legioncodeinc/slack-app-stinger-37---89# slack-app-stinger1011Start with [README.md](README.md) for the workflow map and detailed references.1213The Slack developer playbook for `slack-app-wasp-drone`. Encodes opinionated, research-backed patterns for every major Slack app surface: from first Bolt app scaffold to Marketplace submission.1415## Quick navigation1617| Task | Guide |18|---|---|19| Create a new Slack app, pick HTTP vs Socket Mode | `guides/00-setup-and-bolt.md` |20| Add a slash command | `guides/01-slash-commands.md` |21| Build Block Kit messages and interactive components | `guides/02-block-kit.md` |22| Open / push / update modals | `guides/03-modals.md` |23| Subscribe to events, verify webhooks | `guides/04-events-api.md` |24| Multi-workspace OAuth install flow | `guides/05-oauth-install.md` |25| Submit to App Directory / Marketplace | `guides/06-app-directory.md` |2627## Critical directives2829These are the non-negotiables. Violating any of them is the most common cause of production Slack app failures. See the relevant guide for code patterns.30311. **Acknowledge Slack payloads within 3 seconds, then dispatch async for long-running work.** Slack retries unacknowledged payloads up to 3 times and flags unreliable apps. This applies to slash commands, interactive component actions, and Events API deliveries equally. Source: `research/external/2026-05-20-events-api-verification.md`, `research/external/2026-05-20-slash-commands-interactive.md` (source-repository research, not shipped with the plugin).32332. **Verify Slack request signatures before processing any payload.** Bolt does this automatically. Custom HTTP handlers (Express, FastAPI routes) must implement HMAC-SHA256 verification manually using the app's signing secret. Source: `research/external/2026-05-20-events-api-verification.md` (source-repository research, not shipped with the plugin).34353. **Never store Slack tokens in plaintext config files or committed environment variables.** Bot tokens (`xoxb-`) and signing secrets go in an environment variable manager or secrets vault. Source: `research/external/2026-05-20-bolt-sdk-setup-patterns.md` (source-repository research, not shipped with the plugin).36374. **Always validate the `state` parameter in OAuth callbacks.** Bolt auto-generates and validates `state` via `stateSecret`. Bypassing this validation is a CSRF vulnerability that allows workspace installation hijacking. Source: `research/external/2026-05-20-oauth-multi-workspace.md` (source-repository research, not shipped with the plugin).38395. **Deduplicate Events API payloads using `event_id` before processing.** Slack delivers events at-least-once. Store the `event_id` (Redis SETNX, DB unique constraint) and discard duplicates. Source: `research/external/2026-05-20-events-api-verification.md` (source-repository research, not shipped with the plugin).40416. **If the app will be distributed commercially at scale, use HTTP mode and plan for Marketplace submission from the start.** Socket Mode apps cannot be listed in the Slack Marketplace. Apps intended for commercial distribution must go through Marketplace review (December 2024 policy update). Source: `research/external/2026-05-20-socket-mode-vs-http.md`, `research/external/2026-05-20-dev-policy-update.md` (source-repository research, not shipped with the plugin).42437. **Never use Slack data to train LLMs.** This is an explicit, absolute prohibition in the December 2024 Slack App Developer Policy update ("under any circumstances"). AI-powered Slack bots must not route user message content through LLM training pipelines. Source: `research/external/2026-05-20-dev-policy-update.md` (source-repository research, not shipped with the plugin).4445## Scope note4647This stinger covers the **Bolt SDK (JS, Python, Java)** and the classic Slack Platform. The **Deno Slack SDK** and the next-generation **Workflow Builder platform** are distinct products with separate documentation and are out of scope here. When developers encounter both in the official docs, direct them to `https://tools.slack.dev/bolt-js/` (Bolt JS) vs `https://tools.slack.dev/deno-slack-sdk/` (Deno/Workflow Builder) for the right starting point.4849## Handoff map5051- Deployment infrastructure for the Bolt app backend (Lambda, Fly.io, Render): route to `devops-wasp-drone`.52- Token vault, signing secret rotation, security audit: route to `security-wasp-drone`.53- Django or FastAPI backend decisions beyond Bolt integration: route to `python-wasp-drone`.54- Slack Connect or Enterprise Grid administration: out of scope; direct the user to Slack's enterprise documentation.5556---5758*Forged by `stinger-forge` from `ai-tools/command-briefs/slack-app-wasp-drone-command-brief.md` and `research/`. Part of the Wasp Nest.*