- Home
- Skills
- APIs & Backend
- Slack App Safety Check
More screenshots
Works with the AI Agents you already use
Slack App Safety Check
This skill finds those and eleven other Slack app mistakes before you deploy, and tells you how to fix each one.
$5
Slack App Safety Check
Example session with this skill installed
Check this project with slack-app-safety-check.
- Read your context and instructions
- Compiled the slack app safety
$ python3 scripts/check_slack.py examples/risky
BLOCK bolt-app/app.js:5 K01 SLACK_TOKEN_IN_CODE
token: "<redacted>",
Why: A Slack token (xoxb- bot, xoxp- user, xapp- app-level, or an xoxe- rotating or refresh token) is written in a code, manifest, env, config or CI file that git would commit. Anyone who can read the repository, a build log or the shipped bundle can read channels, post messages and act as your app or user with every scope the token has, until the token is revoked.
Safer: Load tokens from environment variables or a secret manager (SLACK_BOT_TOKEN, SLACK_APP_TOKEN), keep .env files out of git, revoke the committed token and issue a new one (reinstall the app or regenerate the app-level token), and turn on token rotation.
BLOCK bolt-app/app.js:7 K05 BOLT_SIGNATURE_CHECK_OFF
BLOCK bolt-app/oauth.js:7 K02 SLACK_SECRET_IN_CODE
BLOCK services/alerts/app.py:6 K03 WEBHOOK_URL_IN_CODE
BLOCK services/alerts/app.py:13 K04 SLACK_REQUESTS_NOT_VERIFIED
REVIEW bolt-app/app.js:12 K17 MASS_MENTION_WITH_USER_TEXT
REVIEW bolt-app/manifest.json:26 K15 BROAD_SCOPES
REVIEW bolt-app/manifest.json:31 K16 PLAIN_HTTP_SLACK_URL
REVIEW bolt-app/oauth.js:10 K16 PLAIN_HTTP_SLACK_URL
REVIEW bolt-app/oauth.js:12 K15 BROAD_SCOPES
REVIEW bolt-app/oauth.js:14 K18 OAUTH_STATE_CHECK_WEAK
REVIEW legacy-hooks/middleware/verify-slack.js:5 K11 NO_TIMESTAMP_LIMIT
REVIEW legacy-hooks/middleware/verify-slack.js:8 K12 SIGNATURE_COMPARED_WITH_EQUALS
REVIEW legacy-hooks/routes/commands.js:6 K14 VERIFICATION_TOKEN_ONLY
REVIEW legacy-hooks/routes/interactive.js:6 K13 VERIFICATION_NOT_SEEN
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 7 files, 7 with Slack app content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A Flask route that answers Slack's url_verification challenge but never checks X-Slack-Signature accepts fake events and button clicks from anyone who finds the URL, and one signatureVerification: false in a Bolt app does the same. This skill finds those and eleven other Slack app mistakes before you deploy, and tells you how to fix each one.
Your agent runs a scanner on JavaScript, TypeScript and Python files that use Slack (Bolt, slack_sdk, @slack/web-api, Slack tokens, URLs, headers or request fields only Slack sends), on Slack app manifests in JSON or YAML, and on env, config and CI files for tokens and webhook URLs. It knows Bolt's defaults (the signature check is on unless you turn it off, Socket Mode needs none), the verification helpers in slack_sdk and @slack/bolt, edge frameworks that verify by default, and when a check may live in middleware, a hook, a decorator or a helper it cannot read (then it says REVIEW, not BLOCK). It reads .gitignore, so a token in a .env file that git ignores is counted in one line instead of reported. Placeholders from Slack's docs are ignored, comments and test files are skipped, and nothing is run or sent to Slack. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Tokens, secrets and webhook URLs are never printed.
What it checks
BLOCK
- K01: Slack tokens (xoxb, xoxp, xapp, rotating and refresh tokens) in code, manifests, env, config or CI files git would commit
- K02: signing secrets, client secrets or verification tokens written as literals or literal fallbacks in code
- K03: incoming webhook or workflow webhook URLs in code, env, config or CI files git would commit
- K04: a whole-server file that handles Slack events, slash commands or interactivity with nothing that could check X-Slack-Signature
- K05: Bolt's signature check turned off (signatureVerification: false, request_verification_enabled=False) outside Socket Mode
REVIEW
- K11: a hand-made signature check with no five-minute timestamp limit
- K12: a hand-made signature check that compares with == instead of a constant-time function
- K13: a Slack request handler whose signature check, if any, lives in middleware, hooks, decorators, helpers or files the scan cannot read
- K14: handlers that trust the deprecated verification token
- K15: admin scopes and user-token history or search scopes (also optional scopes) in manifests and OAuth settings
- K16: http (not https) OAuth redirect, Events, interactivity and slash command URLs
- K17: @channel, @here or @everyone messages, or link_names, whose call carries user or request text
- K18: OAuth state verification turned off or the state secret written in the code
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and Slack documentation link for each rule
- A risky and a safe example Slack app (Bolt app, manifest, Flask service and Express routes), and the real report the scanner produces on the risky one
Limits It reads each file as written: settings made in Slack's app configuration pages, values from environment variables or other modules, and what middleware or helpers in other files actually do are not seen. A handler that never names Slack is not checked. Only JavaScript, TypeScript and Python code is read; Bolt for Java and apps in Go, Ruby or PHP are not checked. Env, config and CI files are read for tokens and webhook URLs only. One finding is shown per rule and line. Test files are skipped. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Static check of JavaScript, TypeScript, Python, manifest, env, config and CI text. Middleware in other files, Slack app settings made in the browser and environment values are not followed. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert Slack credentials (marked NOTREAL, EXAMPLE or not-a-real, in shapes that common secret scanners do not match) and example.com hosts for the scanner to find. Nothing is run and nothing is sent to Slack.