From slack
Creates, runs, and manages Slack apps from the terminal — local development, app lifecycle, manifest edits, Web API calls, and searching Slack developer docs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/slack:slack-cliThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the Slack CLI to create, run, and manage Slack apps — including calling Web API methods directly and searching Slack developer documentation from the terminal.
Use the Slack CLI to create, run, and manage Slack apps — including calling Web API methods directly and searching Slack developer documentation from the terminal.
For initial setup (sandbox creation, project scaffolding from templates), use the slack-developer:create-slack-app skill instead.
Resolve the path to the public Slack CLI before running any other command. We refer to the resolved value as SLACK_CMD — substitute it everywhere below. Try 1a → 1b → 1c in order; do not skip ahead.
The official install scripts place the binary at a fixed per-user path. If the file exists, use it directly: only the install script writes to that path.
~/.slack/bin/slack%USERPROFILE%\AppData\Local\slack-cli\bin\slack.exe (or %USERPROFILE%\.slack-cli\bin\slack.exe as a fallback)POSIX shell:
[ -x "$HOME/.slack/bin/slack" ] && echo "$HOME/.slack/bin/slack"
PowerShell:
$p = "$env:USERPROFILE\AppData\Local\slack-cli\bin\slack.exe"
if (Test-Path $p) { $p } elseif (Test-Path "$env:USERPROFILE\.slack-cli\bin\slack.exe") { "$env:USERPROFILE\.slack-cli\bin\slack.exe" }
If a path is returned, set SLACK_CMD to that absolute path and proceed to Step 2. Do not also run _fingerprint.
slack on PATH (verify with fingerprint)If 1a found nothing, try slack on PATH:
slack _fingerprint 2>/dev/null
If it outputs d41d8cd98f00b204e9800998ecf8427e, set SLACK_CMD=slack and proceed.
If 1b fails or returns a different value, ask the developer using AskUserQuestion:
slack command on your system doesn't appear to be the public Slack CLI. Do you have it installed under a different name or alias?"<alias> _fingerprint 2>/dev/null and set SLACK_CMD=<alias>.curl -fsSL https://downloads.slack-edge.com/slack-cli/install.sh | bash
Then re-run 1a — the install script will have written ~/.slack/bin/slack.Common mistakes: Don't use which slack to discover the binary — which resolves any shell alias and defeats the point of 1a. In Git Bash on Windows, use the POSIX probe form, not PowerShell.
Always run SLACK_CMD <command> --help before constructing a command you have not used in the current session. Do not guess at flags — the help output is the source of truth.
SLACK_CMD help — lists all available command groupsSLACK_CMD <command> --help — shows subcommands, flags, and usage examples--app and --team valuesWhen a command requires --app or --team:
SLACK_CMD app list from the project directory to see installed apps and their IDs.SLACK_CMD auth list to see authenticated workspaces and their team IDs.slack docs search)Search Slack's developer documentation directly from the terminal.
SLACK_CMD docs search "<query>" --output=text --limit=5
Use --output=text for concise terminal-readable results. Use this:
slack api)Call any Slack Web API method directly. Run SLACK_CMD api --help for full details and examples.
Parameters are passed as positional key=value pairs (NOT --key=value flags):
SLACK_CMD api chat.postMessage channel=C0123456789 text="Hello from the CLI"
Important distinction: --team, --token, --json, and --data are meta-flags (prefixed with --). API method parameters use positional key=value syntax without dashes.
Reference: Full method list at https://docs.slack.dev/reference/methods.md.
slack auth)SLACK_CMD auth list
slack login is interactive — it requires browser interaction and cannot be run by the coding agent or in the background. Tell the developer to run in a new terminal window:
SLACK_CMD login
This will:
/slackauthticket commandWait for the developer to confirm login succeeded, then verify with SLACK_CMD auth list.
Use --team <team_id> on individual commands to target a specific workspace without switching globally.
slack run)Run SLACK_CMD run --help for all available flags.
Run SLACK_CMD app list from the project directory to check for installed apps:
--app=<app_id> in the run command.--team=<team_id> instead (get the team ID from SLACK_CMD auth list).Run this command as a background process so the developer can continue working:
If an app ID was found:
cd <project-dir> && SLACK_CMD run --org-workspace-grant=all --app=<app_id>
If no apps — use the team ID:
cd <project-dir> && SLACK_CMD run --org-workspace-grant=all --team=<team_id>
Tell the developer the app is running in the background. They can ask:
Run SLACK_CMD manifest --help for subcommands (validate, info) and the --source local|remote flag.
Use SLACK_CMD manifest validate before deploying or when something seems wrong with the app configuration.
For any other command group (e.g., trigger, datastore, env, collaborator, external-auth, deploy), run SLACK_CMD <command> --help to discover subcommands and flags. Run SLACK_CMD help to see all available command groups.
SLACK_CMD is a placeholder — always substitute the actual command name resolved in Step 1.--help before constructing a command you have not used in the current session.slack login, slack trigger create without --trigger-def) cannot be run in the background. Tell the developer to run these in a new terminal window.slack run runs locally for development. slack deploy deploys to Slack's hosted infrastructure. These are different operations — do not confuse them.npx claudepluginhub anthropics/claude-plugins-official --plugin slackBootstraps an aweek-branded Slack app via API, provisions Socket-Mode and bot tokens, and persists credentials to enable Claude chats through `aweek serve` SlackAdapter.
Guides developers through creating a Slack app or agent using Bolt for JS or Python — prerequisites, sandbox setup, auth, project scaffolding, and local dev.
Builds Slack apps with the Bolt framework in Python, JavaScript, or Java. Covers Block Kit UIs, slash commands, event handling, OAuth, and Workflow Builder integration.