From slack
Interactive setup wizard for Slack plugin. Guides users through obtaining and configuring Slack credentials (workspace, token, cookie) from their browser session.
How this skill is triggered — by the user, by Claude, or both
Slash command
/slack:skills/slack-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactive setup wizard that guides users through configuring the Slack plugin. This skill should be called when `slack-status` indicates missing or invalid configuration.
Interactive setup wizard that guides users through configuring the Slack plugin. This skill should be called when slack-status indicates missing or invalid configuration.
Automatically trigger when:
User requests:
When the user needs to set up Slack, follow these steps:
First, ensure the config file exists by copying from the template:
PLUGIN_ROOT="$HOME/.claude/plugins/marketplaces/djalmaaraujo-claude-code-plugins/plugins/slack"
if [ ! -f "$PLUGIN_ROOT/config.json" ]; then
cp "$PLUGIN_ROOT/example.config.json" "$PLUGIN_ROOT/config.json"
chmod 600 "$PLUGIN_ROOT/config.json"
echo "Created config.json from template"
fi
PLUGIN_ROOT="$HOME/.claude/plugins/marketplaces/djalmaaraujo-claude-code-plugins/plugins/slack"
STATUS=$("$PLUGIN_ROOT/skills/slack-status/check.sh")
echo "$STATUS"
Explain to the user that you need 3 pieces of information from their Slack browser session:
a8c.slack.com, mycompany.slack.com)xoxc-)xoxd-)Tell the user:
"I'll guide you through getting your Slack credentials from your browser. This is safe - we're using your existing Slack session credentials."
Instructions for getting credentials:
1. Open Slack in Chrome and go to your workspace
2. Open DevTools:
- Mac: Cmd + Option + J
- Windows/Linux: Ctrl + Shift + J
3. Go to the "Network" tab in DevTools
4. Send any message in Slack (just type "test" anywhere)
5. In the Network tab, find a request called "chat.postMessage" or "api"
6. Click on it and look for:
From the "Payload" or "Form Data" section:
→ token: Copy the value starting with "xoxc-..."
From the "Headers" section, find "Cookie":
→ Look for "d=" and copy everything after it until the next semicolon
→ This starts with "xoxd-..."
From the URL or request:
→ workspace: Your workspace domain (e.g., "a8c.slack.com")
Use the AskUserQuestion tool to collect the three pieces of information:
Question 1: Workspace
"What is your Slack workspace URL?"
Example: a8c.slack.com or mycompany.slack.com
(Just the domain, not the full URL)
Question 2: Token
"Please paste your Slack token (starts with xoxc-)"
This is found in the DevTools Network tab → Form Data → token field
Question 3: Cookie
"Please paste your Slack cookie (starts with xoxd-)"
This is found in the DevTools Network tab → Headers → Cookie → d= value
Once you have all three credentials, validate and save them:
PLUGIN_ROOT="$HOME/.claude/plugins/marketplaces/djalmaaraujo-claude-code-plugins/plugins/slack"
WORKSPACE="a8c.slack.com" # from user
TOKEN="xoxc-..." # from user
COOKIE="xoxd-..." # from user
# Use the shared lib to save config
source "$PLUGIN_ROOT/lib/config.sh"
save_config "$WORKSPACE" "$TOKEN" "$COOKIE"
# Verify it works
STATUS=$("$PLUGIN_ROOT/skills/slack-status/check.sh")
if echo "$STATUS" | grep -q "^OK"; then
echo "✅ Slack setup complete!"
echo "Details: $STATUS"
else
echo "❌ Setup failed. Please try again."
echo "Error: $STATUS"
fi
After successful setup, inform the user:
✅ Slack plugin is now configured!
Your credentials have been saved to:
~/.claude/plugins/marketplaces/djalmaaraujo-claude-code-plugins/plugins/slack/config.json
You can now use:
- /slack:slack-search-user - Find Slack users
- /slack:slack-send-message - Send messages and DMs
Your credentials are stored securely and only accessible to you.
Explain to users:
If validation fails:
invalid_auth - Token or cookie is incorrect
token_expired - Session expired
API errors - Network or Slack issues
If the user prefers, they can create the config file manually:
PLUGIN_ROOT="$HOME/.claude/plugins/marketplaces/djalmaaraujo-claude-code-plugins/plugins/slack"
# Copy template to config
cp "$PLUGIN_ROOT/example.config.json" "$PLUGIN_ROOT/config.json"
chmod 600 "$PLUGIN_ROOT/config.json"
# Edit the config file with your credentials
# Replace the placeholder values with your actual workspace, token, and cookie
Then verify with:
~/.claude/plugins/marketplaces/djalmaaraujo-claude-code-plugins/plugins/slack/skills/slack-status/check.sh
users array will be populated automatically as you search for usersnpx claudepluginhub djalmaaraujo/claude-code-plugins --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.
Creates, runs, and manages Slack apps from the terminal — local development, app lifecycle, manifest edits, Web API calls, and searching Slack developer docs.
Interact with Slack workspaces via CLI using bot tokens: send messages, list/read channels, manage reactions, multi-bot auth for CI/CD and agents.