bolt-js-slack-mcp-server: Skill for Claude Code

.agents/skills/test-slack-app/SKILL.md

test-slack-app is a skill for Claude Code, Codex from slack-samples/bolt-js-slack-mcp-server. It costs 111 tokens per session (2,204 once invoked), scanned A, a copy of test-slack-app, MIT.

A guided manual check for a Slack app, either created with the Slack CLI or built as a Bolt app. It runs the app in a developer sandbox or Free Team and has the developer exercise its real commands, shortcuts, or events.

In plain words
What is it for?
Use it to set up a safe test workspace, follow concrete actions in Slack, and verify the app's observed responses.
Why use it?
It confirms that an already-built app responds in Slack without exposing tests to a workspace used by real coworkers. It is a hands-on smoke test, not an automated test suite.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is slack-samples/bolt-js-slack-mcp-server's own configuration. It tells Claude Code and Codex how to work on bolt-js-slack-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bolt-js-slack-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to slack-samples/bolt-js-slack-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/slack-samples/bolt-js-slack-mcp-server/main/.agents/skills/test-slack-app/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/slack-samples/bolt-js-slack-mcp-server

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for test-slack-app

README.md
[![agentmods](https://agentmods.dev/badge/skills/slack-samples/bolt-js-slack-mcp-server/test-slack-app/github.svg)](https://agentmods.dev/skills/slack-samples/bolt-js-slack-mcp-server/test-slack-app)
Your own site
<a href="https://agentmods.dev/skills/slack-samples/bolt-js-slack-mcp-server/test-slack-app"><img src="https://agentmods.dev/badge/skills/slack-samples/bolt-js-slack-mcp-server/test-slack-app/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for test-slack-app

Your own site · 80×15
<a href="https://agentmods.dev/skills/slack-samples/bolt-js-slack-mcp-server/test-slack-app"><img src="https://agentmods.dev/badge/skills/slack-samples/bolt-js-slack-mcp-server/test-slack-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00111 $0.02204
Opus 5.5 $0.00044 $0.00882
Sonnet 5.5 $0.00022 $0.00441
Haiku 4.5 $0.00011 $0.00220

Measured yesterday against content hash 37252264d344, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-slack-app scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to test-slack-app — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/test-slack-app/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Slack App

Help a developer confirm that a Slack app they already built actually works. This is the last step of the build loop, after the create-slack-app skill scaffolds an app and the slack-cli skill runs it.

The approach is simple and safe:

  1. Run the app in a developer sandbox or a Free Team: a sandbox for preference, or a Free Team the developer created for this. Never a workspace with real coworkers in it.
  2. Read the app's source to learn what it actually listens for.
  3. Hand the developer concrete steps to perform in Slack, then help them confirm the app responds.

This is guided manual checking, not an automated test suite: you drive the setup and tell the developer what to type or click, and they confirm what they see. It works best for apps managed by the Slack CLI; there is a best-effort path for plain Bolt apps in Step 2.


Step 1: Set Up a Safe Place to Test

1a. Detect the Slack CLI

Load the slack-cli skill (with your skill tool, if you have one) before running any command, and follow its Step 1: Detect the Slack CLI to check whether the public Slack CLI is installed and resolve its command name. Don't check for the CLI yourself first: a slack on PATH isn't always the public CLI, and that step tells them apart. The fingerprint check, alias fallback, and install instructions all live there; do not duplicate them here. Refer to the resolved command as SLACK_CMD throughout. If the CLI is not installed, guide the developer through that same step to install it, since running the app needs it.

1b. Make sure there is a safe workspace to test in

Testing belongs in a workspace nobody is working in: a developer sandbox for preference, or a Free Team the developer created for this. Never a workspace with real coworkers in it.

  • Explain it from the live docs, not from here. Use the slack-docs skill to fetch and summarize https://docs.slack.dev/tools/developer-sandboxes.md, so the recommendation always reflects the current docs rather than a copy that drifts out of date. Tell the developer that Slack recommends a sandbox for building and testing apps.
  • Find the current target. Run SLACK_CMD auth list for the authenticated workspaces and their team IDs, and, from the project directory, SLACK_CMD app list for the apps already installed and their IDs.
  • Confirm the target is safe. The CLI cannot tell a sandbox, a Free Team, and a workspace full of real users apart, so ask the developer which one they are pointed at. A sandbox or a Free Team they created for this is fine. A workspace with coworkers in it is not: stop and get them onto one of the other two.
  • If there is no safe target yet, set one up with the create-slack-app skill (Step 3: Choose Where to Install the App), which owns the ranked targets, the sandbox list / sandbox create flow, and the Developer Program links. Either path finishes in the browser, so have the developer come back here once the workspace exists and they have logged into it.

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 112 lines · 111 tokens per session scan A 37252264d344

Subscribe to this mod's changes

test-slack-app is a skill published in the GitHub repository slack-samples/bolt-js-slack-mcp-server (17 stars, last pushed yesterday), licensed MIT. It adds 111 tokens to every session and 2,204 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to test-slack-app, differing in 0 lines, and is treated as a copy.

Related

test-slack-app compared with skills from other repositories

test-slack-app next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
test-slack-appslack-samples/bolt-js-slack-mcp-serverSkill17yesterdayMITA111Claude Code, Codex
create-verification-skillYeachan-Heo/oh-my-claudecodeSkill41ktodayMITA45Claude Code
verify-omnigentomnigent-ai/omnigentSkill11ktodayApache-2.0A100Claude Code, Codex
test-masterJeffallan/claude-skillsSkill12kyesterdayMITA104Claude Code
eval-dataset-designbojieli/ai-agent-bookSkill59k1mo agoApache-2.0A138Claude Code, Codex
dogfoodcallstack/agent-deviceSkill5.4ktodayMITA55Claude Code
cua-driverdavidondrej/skillsSkill4.3ktodayMITA68Claude Code, Codex