Skip to content
Skills Library
Programming · Testing

slack-bot-e2e

/slack-bot-e2e

End-to-end test any Slack bot through a real Slack test channel. Posts a message (with files, in threads) that mentions the bot, delivers a correctly signed app_mention or message event to the bot's Events API URL as a chosen user, waits for the bot's reply in Slack and checks it against a regex. Use when a change touches how a Slack bot receives events, reads threads or files, or replies, or when asked for a Slack e2e, a Slack smoke test, or "test it in Slack". Works with any HTTP Events API bot (Bolt, custom, local or deployed); not for Socket Mode.

Licence
MIT
Last repository change
30.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/slack-e2e.mjs

What it does and when to use it

End-to-end test any Slack bot through a real Slack test channel. Posts a message (with files, in threads) that mentions the bot, delivers a correctly signed app_mention or message event to the bot's Events API URL as a chosen user, waits for the bot's reply in Slack and checks it against a regex. Use when a change touches how a Slack bot receives events, reads threads or files, or replies, or when asked for a Slack e2e, a Slack smoke test, or "test it in Slack". Works with any HTTP Events API bot (Bolt, custom, local or deployed); not for Socket Mode.

Triggers from the description

s Events API URL as a chosen user, waits for the bottest it in Slack
Original author description

End-to-end test any Slack bot through a real Slack test channel. Posts a message (with files, in threads) that mentions the bot, delivers a correctly signed app_mention or message event to the bot's Events API URL as a chosen user, waits for the bot's reply in Slack and checks it against a regex. Use when a change touches how a Slack bot receives events, reads threads or files, or replies, or when asked for a Slack e2e, a Slack smoke test, or "test it in Slack". Works with any HTTP Events API bot (Bolt, custom, local or deployed); not for Socket Mode.

How it works

  1. Set up
  2. Commands
  3. Writing a check
  4. Limits
Original SKILL.md headings · 54 lines, 612 words
SKILL.md preview
---
name: slack-bot-e2e
description: End-to-end test any Slack bot through a real Slack test channel. Posts a message (with files, in threads) that mentions the bot, delivers a correctly signed app_mention or message event to the bot's Events API URL as a chosen user, waits for the bot's reply in Slack and checks it against a regex. Use when a change touches how a Slack bot receives events, reads threads or files, or replies, or when asked for a Slack e2e, a Slack smoke test, or "test it in Slack". Works with any HTTP Events API bot (Bolt, custom, local or deployed); not for Socket Mode.
---

# Slack bot e2e

`scripts/slack-e2e.mjs` drives a Slack bot through the real Slack path with no person at the keyboard. It needs only Node 20+ and no dependencies.

A Slack app cannot trigger its own `app_mention`. `send` therefore posts the visible message with the bot's own token, then signs an `app_mention` event for that message with the app's signing secret, as `SLACK_E2E_USER_ID`, and POSTs it to the bot's Events API URL. The bot cannot tell it apart from a real event. Everything after that is real: the bot's handler, its thread and file reads from Slack, and the reply it posts back, which the script reads from the thread.

## Set up

1. Create or reuse a dedicated test Slack app and a test channel. Invite the bot to the channel. Never point this at a production channel: every command posts real messages.
2. The bot token needs `chat:write`, `files:write`, `files:read` and `channels:history` (`groups:history` for a private channel).
3. Run the bot under test so its Events API endpoint is reachable from this machine (for example `http://localhost:3000/slack/events`). Localhost works: the script posts the event itself, so no tunnel is needed.
4. Export the variables, or keep them in a `.env` and run with `node --env-file=.env`:

   | Variable | Value |
   | --- | --- |
   | `SLACK_E2E_BOT_TOKEN` | the bot under test's `xoxb-` token |
   | `SLACK_E2E_SIGNING_SECRET` | that app's signing secret |
   | `SLACK_E2E_CHANNEL_ID` | test channel ID (`C…`) |
   | `SLACK_E2E_USER_ID` | the human user the events claim to come from (`U…`) |
   | `SLACK_E2E_EVENTS_URL` | the bot's Events API URL |

5. Run `whoami` to confirm the token resolves to the expected bot, team and app.

## Commands

`S` is this skill's `scripts/slack-e2e.mjs`.

```bash
node S whoami
node S send --text "Total revenue in the attached CSV?" --file /tmp/sales.csv --expect "\\b400\\b"
node S post --text "The launch code is PELICAN" --deliver
node S send --thread <threadTs> --text "What is the launch code?" --expect pelican
node S read --thread <threadTs>
```

- `send` prefixes `<@bot>`, posts, delivers a signed `app_mention`, then polls the thread until the bot's replies after the mention stop changing and none is still streaming. It prints JSON with `eventId`, `ts`, `threadTs`, `replies`, `failures` and `passed`, and exits 1 on no reply within `--timeout` seconds (default 180) or a reply that does not match `--expect` (case-insensitive regex over all replies joined).
- `post` posts without a mention, to set up thread context. `--deliver` also sends a signed `message` event, for bots that capture channel history from events. Use its `threadTs` with `--thread` on the next `send` for a same-thread check.
- `read` prints every message in a thread with its user, files, reactions and streaming state.

## Writing a check

- Make the answer impossible to guess: exact numbers from a fixture, a code inside an image, a word only the thread contains.
- One behaviour per `send`. Put context in the thread with `post` first rather than in the mention.
- Read `failures` and the bot's own logs before changing anything.
- Paste the JSON of each passing check into the PR as evidence.

## Limits

- Only the event delivery is synthetic. Slack's retries, Event Subscriptions URL verification and button clicks (interactivity payloads) need a person and a public URL.
- The fake event carries the message's real `ts` and `files`, but `user` is whatever `SLACK_E2E_USER_ID` says; Slack itself shows the message as posted by the bot.
- Socket Mode bots have no HTTP endpoint, so `send` cannot reach them.
- Replies are matched by the bot's user ID, so a bot that replies with a different token or as another user is not seen.
Files in this package (2)
  • SKILL.md 4 KB
  • scripts/slack-e2e.mjs 7 KB

Versions

The database has no other skills named slack-bot-e2e.

Database snapshot: 13.11.2026 · package version d1c8b9ad543c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100using-slack
    Use when sending, reading, or reacting to Slack messages, watching for bot events (mentions, DMs, reactions, thread replies), downloading Slack files, or provisioning/creating/deploying a new Slack bot — all from the command line via the slackline CLI.
  • 100slack-expert
    Expert in Slack bot development, Block Kit UI, Events API, slash commands, OAuth flows, and app distribution. Use when the user mentions communication, collaboration, bots, API, Slack bot, or Block Kit, or when the task involves Slack Platform, Development Tools, Slack Bot with…
  • 100slack-bot-builder
    Builds Slack bots and integrations using the Slack API (Bolt framework). Use when the user wants to create a Slack bot, build slash commands, handle Slack events, send messages to channels, build interactive modals/blocks, create Slack workflows, or integrate services with…
  • 100slack-development
    Implement Slack bot behavior with correct Slack-documented message formats, inbound mention/event routing, and long-running task UX. Use when asked to "format Slack messages", "fix Slack markdown", "debug thread mentions", "improve Slack bot UX", "add streaming in Slack", or…
  • 100slack-bot-creator
    Create slack bot creator operations. Auto-activating skill for Business Automation. Triggers on: slack bot creator, slack bot creator Part of the Business Automation skill category. Use when working with slack bot creator functionality. Trigger with phrases like "slack bot…
  • 100slack-channel
    Slack for a Pots bot. How to connect a Slack workspace yourself (the Slack app, its tokens, bot.json), send and edit messages, call Slack's Web API, files and limits, and how to post buttons, menus, tables and forms with Block Kit, get clicks and mark a question answered. Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.