← ClaudeAtlas

slacklisted

Use when user references Slack, *.slack.com/archives/ URLs, channel mentions like #deploys, or asks to post/thread/upload-file/fetch-history/send deploy or incident alert. Multi-workspace via SLACK_PROFILE.
tuannv14/claude-team-toolkit · ★ 1 · DevOps & Infrastructure · score 70
Install: claude install-skill tuannv14/claude-team-toolkit
# /slack — Slack Web API (multi-workspace) REST against `https://slack.com/api/`. Bearer auth with bot OAuth token. Profiles isolate workspaces. Profile resolution: `--profile` → `SLACK_PROFILE` → `~/.slack/active_profile` → `[default]`. ## Overview REST against Slack Web API with bot OAuth tokens (`xoxb-`). Profiles isolate workspaces. Default to bot tokens — never use user tokens (`xoxp-`) which carry the user's full permissions. ## When to Use - Posting deploy / incident alerts to channels - Threaded replies to existing messages (incident timelines) - Block Kit rich messages (status dashboards, deploy summaries) - File uploads (logs, screenshots) for incident triage - Fetching channel history for context ## When NOT to Use - Real-time event consumption → use Events API + your own server, not REST - Slash command handlers → that's an HTTP webhook, not API client - Complex workflows → Slack Workflow Builder or Bolt SDK - Direct messages to users at scale → looks spammy, against TOS ## Dependencies `curl`, `jq`. ## Profile config `~/.slack/credentials` (mode 600): ```ini [default] bot_token = xoxb-xxxxxxxxxxxx-xxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx default_channel = #general [work] bot_token = xoxb-xxxxxxxxxxxx-xxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx default_channel = #engineering require_confirm = true # gate every post ``` **Get a bot token:** 1. https://api.slack.com/apps → Create New App → From scratch 2. OAuth & Permissions → add bot scopes