Terminal
Terminal/Skill
Walks you through creating a Slack app or agent with the Slack CLI, from setup and workspace choice to a JavaScript or Python starter project.
By Slack
Works with
npx skills add slackapi/slack-skills-plugin --skill create-slack-appHelp the developer create a Slack app or agent using Bolt for $0.
This skill walks through the full setup: prerequisites, authentication, choosing a workspace to install into, project scaffolding from a template, and running the app locally.
Use the slack:slack-cli skill — Step 1: Detect the Slack CLI — to check whether the public Slack CLI is installed and resolve its command name. The fingerprint check, alias fallback, and install instructions all live there; do not duplicate them here.
Once resolved, use the detected command name for all CLI commands throughout the rest of this skill. We refer to it as SLACK_CMD below — substitute the actual resolved command name everywhere you see SLACK_CMD.
Run SLACK_CMD version and print the version to confirm everything is working before continuing.
$0 is bolt-js: Run node --version to verify Node.js is installed (v18+ required). If not installed, suggest brew install node or point to https://nodejs.org.$0 is bolt-python: Run python3 --version to verify Python is installed (3.6+ required). If not installed, suggest brew install python3 or point to https://python.org.Use the slack:slack-cli skill — Step 5: Authentication (slack auth) — to check the developer's auth status and walk them through SLACK_CMD login if they're not already authenticated.
Wait for confirmation that authentication succeeded before proceeding.
The app needs a Slack workspace to install into. Three targets work and they are not equivalent. Use AskUserQuestion to let the developer pick, presenting them in this order:
| Target | Best for | Cost of entry |
|---|---|---|
| Developer sandbox (recommended) | Anything the developer plans to keep building on. A free Enterprise Grid org isolated from real users, so org-level features are testable. | Needs a Slack Developer Program account, which is free to join. Every account can create a basic sandbox, with no paid plan or payment method. |
| Free Team (second choice) | Starting right now, when Developer Program signup is the thing in the way. A free workspace the developer creates and owns. | Capped at 10 apps per workspace, and no Enterprise Grid org features. |
| Existing production workspace (last resort) | Only when the app must reach real data or real coworkers. | Usually gated by admin approval, and the developer may not be the admin. |
Then follow the matching sub-step below. Whichever target they pick, authentication is the same Step 2 flow: the /slackauthticket command works in any workspace the developer belongs to, so there is no sandbox-specific login.
Whichever sub-step you follow, wait for confirmation that a target workspace exists and is authenticated before proceeding.
List existing sandboxes. Pass --team so the CLI does not stop to ask which authentication to use (get the team ID from SLACK_CMD auth list):
SLACK_CMD sandbox list --team <team_id>
If the developer has no Developer Program account, sandbox list returns nothing useful, because sandboxes belong to the developer program account whose email matches the authenticated user rather than to the workspace. If they say they do have an account, check that the email they are logged in with matches it before sending them to sign up, and log into a workspace under that email if not. Point them at https://api.slack.com/developer-program/join, and offer the Free Team path in 3b as a way to start building now rather than waiting on signup.
If a sandbox exists: Show it and confirm they want to use it.
If no sandbox exists: Create one. Ask the developer for a name and a password with AskUserQuestion, then run:
SLACK_CMD sandbox create --team <team_id> --name <sandbox-name> --password <password>
Important: the password is a credential. Do NOT echo it, restate it, or write it into a summary. Pass it straight to the command, the same rule Step 4c applies to API keys.
Sandboxes can also be created in the browser at https://api.slack.com/developer-program/sandboxes.
Once the sandbox exists, have the developer log into it with the Step 2 flow before continuing.
Basic sandboxes. A developer who is not on a paid plan and has not added a payment method gets a basic sandbox. It works for everything this skill builds, with stricter limits: it is archived after 1 month of inactivity, has no Slack Connect, and does not support deploying apps to Slack infrastructure (ROSI). If the developer needs more, they can add a payment method (they are not charged) or join a paid plan, then upgrade the sandbox from https://api.slack.com/developer-program/sandboxes without losing their apps or data. Limits are listed at https://docs.slack.dev/tools/developer-sandboxes#basic.
A Free Team is an ordinary Slack workspace on the free plan. The developer creates one at https://slack.com/get-started, then logs into it with the Step 2 flow.
What to tell them:
service_limits_exceeded.admin.* API methods (which need Business+ or Enterprise Grid), and multi-workspace behaviour generally. If the app targets those, use a sandbox instead.Only when the app genuinely needs real data or real users. Warn the developer before they log in:
SLACK_AUTO_REQUEST_AAA=1 in the environment. It is an environment variable, not a CLI flag.Ask the developer what kind of app they want to build. Present the available templates based on their chosen framework ($0):
| Template | Repo | Description |
|---|---|---|
| Starter Template | slack-samples/bolt-js-starter-template | Basic Bolt JS app — great starting point |
| Starter Agent | slack-samples/bolt-js-starter-agent | Minimal AI agent using Claude/OpenAI |
| Support Agent | slack-samples/bolt-js-support-agent | AI-powered IT helpdesk agent |
| Getting Started | slack-samples/bolt-js-getting-started-app | Official getting started tutorial app |
| Examples | slack-samples/bolt-js-examples | Unified showcase of Slack features |
| Template | Repo | Description |
|---|---|---|
| Starter Template | slack-samples/bolt-python-starter-template | Basic Bolt Python app — great starting point |
| Starter Agent | slack-samples/bolt-python-starter-agent | Minimal AI agent using Claude/OpenAI/Pydantic AI |
| Support Agent | slack-samples/bolt-python-support-agent | AI-powered IT helpdesk agent |
| Assistant Template | slack-samples/bolt-python-assistant-template | Agents & Assistants template |
| Examples | slack-samples/bolt-python-examples | Unified showcase of Slack features |
Use AskUserQuestion to let the developer pick a template. Recommend the Starter Template for first-timers or the Starter Agent if they want to build an AI agent.
If the developer picks Starter Agent or Support Agent, these templates contain subdirectories for different AI providers. Ask the developer which provider they want to use via AskUserQuestion:
bolt-js subdirectories:
| Subdir | Description |
|---|---|
claude-agent-sdk | Uses Anthropic's Claude Agent SDK |
openai-agents-sdk | Uses OpenAI's Agents SDK |
bolt-python subdirectories:
| Subdir | Description |
|---|---|
claude-agent-sdk | Uses Anthropic's Claude Agent SDK |
openai-agents-sdk | Uses OpenAI's Agents SDK |
pydantic-ai | Uses Pydantic AI (supports multiple LLM backends) |
Recommend Claude Agent SDK as the default option.
Ask what they want to name their project (suggest a default like my-slack-app), then run:
For templates WITHOUT subdirectories (Starter Template, Getting Started, Assistant Template, Examples):
SLACK_CMD create <project-name> -t <template-repo>
For agent templates WITH subdirectories (Starter Agent, Support Agent):
SLACK_CMD create <project-name> -t <template-repo> --subdir <chosen-subdir>
For example:
# Non-agent template
SLACK_CMD create my-slack-app -t slack-samples/bolt-js-starter-template
# Agent template with provider subdir
SLACK_CMD create my-slack-agent -t slack-samples/bolt-js-starter-agent --subdir claude-agent-sdk
Confirm the project was created successfully by checking that the directory exists and listing its contents.
If the developer chose an agent template (Starter Agent or Support Agent), they need to set the required API key for their chosen AI provider. Ask for the key value using AskUserQuestion, then set it using the Slack CLI from within the project directory.
Required environment variables by provider:
| Provider | Env Variable | Description |
|---|---|---|
claude-agent-sdk | ANTHROPIC_API_KEY | Anthropic API key |
openai-agents-sdk | OPENAI_API_KEY | OpenAI API key |
pydantic-ai | OPENAI_API_KEY | OpenAI API key (required). Optionally also ANTHROPIC_API_KEY if using Anthropic as the backend — if both are set, Anthropic is used by default. |
Use AskUserQuestion to ask the developer for their API key value(s). Then set each one:
cd <project-name> && SLACK_CMD env set <ENV_VAR_NAME> <value>
For example:
cd my-slack-agent && SLACK_CMD env set ANTHROPIC_API_KEY sk-ant-...
Important: Do NOT store or echo API key values in logs or output. Only pass them directly to SLACK_CMD env set.
Use the slack:slack-cli skill — Step 6: Running an App Locally (slack run) — to resolve the app or team target and start the dev server in the background.
Tell the developer their app is now running and installed in the workspace they chose in Step 3, and that file changes will auto-reload it.
If the install stops on an admin approval request, they picked a workspace with AAA turned on: see Step 3c for the options.
After the app is running, suggest next steps:
SLACK_CMD is a placeholder — always substitute the actual command name resolved in Step 1a (typically slack, but may be an alias).slack deploy (hosted deployment).SLACK_CMD sandbox create prompts for a name and password only when those flags are missing. Supply --team, --name, and --password and it runs non-interactively, so you can run it yourself rather than handing it to the developer. SLACK_CMD sandbox list needs --team for the same reason: without it the CLI prompts for which authentication to use.free_team_not_allowed error is scoped to low-code workflow and function apps, which this skill does not create.SLACK_CMD doctor to diagnose their setup.