Download for MacApple silicon, macOS 14+
Skill

deploy-slack-app

@slackapi Updated 2026-10-22

Use when a developer wants to deploy, host, or run a Slack app somewhere it keeps working after the local process stops, or mentions Railway, Heroku, `railway up`, `git push heroku`, `slack deploy`, a `deploy` hook in `.slack/hooks.json`, hosting a Socket Mode or Request URL (HTTP) Bolt app, deploying from Windows, graduating an app out of a developer sandbox, or tearing down a deployed app.

claude-codecodexcursormcpskillsslack

Install

With your agent

Install OMGSkills skill "slackapi/slack-skills-plugin:skills/deploy-slack-app" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/slackapi/slack-skills-plugin /tmp/slack-skills-plugin && ln -s /tmp/slack-skills-plugin/skills/deploy-slack-app ~/.claude/skills/deploy-slack-app

From README

Deploy Slack App Take a Slack app that already works locally and deploy it to a hosting provider as a separate Slack app, with its own app ID, that keeps running without the developer's machine. The local development app is unchanged, and Step 5: Deploy explains how the two coexist. This is the step after the slack:test-slack-app skill confirms the app responds. The mechanism is the Slack CLI's deploy hook. Adding a deploy key to the project's .slack/hooks.json replaces Slack's own hosted deployment with a script of your choosing, and the CLI runs that script after it has created and installed the deployed app. That ordering is the whole reason this approach is worth using: the app's bot and app-level tokens are already in the script's environment by the time it runs, so nothing here has to prompt for a secret or store one.