> configure
Configure Slack channel tokens (bot token + app-level token)
curl "https://skillshub.wtf/jeremylongshore/claude-code-plugins-plus-skills/configure?format=md"/slack-channel:configure
Overview
Configure the Slack channel MCP plugin by providing your Slack bot token and app-level token. Writes credentials to a secure .env file with owner-only permissions.
Prerequisites
- A Slack app created at api.slack.com/apps with Socket Mode enabled
- A Bot User OAuth Token (
xoxb-...) from OAuth & Permissions - An App-Level Token (
xapp-...) from Socket Mode settings - Write access to
~/.claude/channels/slack/
Usage
/slack-channel:configure <xoxb-bot-token> <xapp-app-token>
Instructions
-
Parse the two arguments from
$ARGUMENTS:- First token must start with
xoxb-(Bot User OAuth Token) - Second token must start with
xapp-(App-Level Token)
- First token must start with
-
If either token is missing or has the wrong prefix, show this error and stop:
Error: Two tokens required. - Bot token (starts with xoxb-) from OAuth & Permissions - App token (starts with xapp-) from Socket Mode settings Usage: /slack-channel:configure xoxb-... xapp-... -
Create the state directory if it doesn't exist:
~/.claude/channels/slack/ -
Write the
.envfile at~/.claude/channels/slack/.env:SLACK_BOT_TOKEN=<bot-token> SLACK_APP_TOKEN=<app-token> -
Set file permissions to owner-only:
chmod 600 ~/.claude/channels/slack/.env -
Confirm success:
Slack channel configured. Start Claude with the Slack channel: claude --channels plugin:slack-channel@claude-code-plugins Or for development: claude --dangerously-load-development-channels server:slack
Security
- Never echo the tokens back in the confirmation message
- Never log tokens to stdout or any file other than
.env - Always set 0o600 permissions on the
.envfile
Output
On success, displays:
Slack channel configured.
Start Claude with the Slack channel:
claude --channels plugin:slack-channel@claude-code-plugins
On validation failure, displays the error with correct usage syntax.
Error Handling
| Error | Cause | Resolution |
|---|---|---|
| Missing token argument | Fewer than 2 arguments provided | Show usage with required token prefixes |
| Invalid bot token prefix | First token does not start with xoxb- | Explain where to find the Bot User OAuth Token |
| Invalid app token prefix | Second token does not start with xapp- | Explain where to find the App-Level Token in Socket Mode settings |
| Permission denied | Cannot write to ~/.claude/channels/slack/ | Check directory permissions and create parent dirs if needed |
Examples
Standard configuration:
/slack-channel:configure xoxb-1234567890-abcdef xapp-1-ABCDEF-ghijkl
→ Slack channel configured.
Missing token error:
/slack-channel:configure xoxb-1234567890
→ Error: Two tokens required.
- Bot token (starts with xoxb-) from OAuth & Permissions
- App token (starts with xapp-) from Socket Mode settings
Resources
- Slack API: Creating an app — app setup walkthrough
- Slack Socket Mode — how to enable and get app-level tokens
- Access control:
/slack-channel:access— configure who can message your session
> related_skills --same-repo
> fathom-cost-tuning
Optimize Fathom API usage and plan selection. Trigger with phrases like "fathom cost", "fathom pricing", "fathom plan".
> fathom-core-workflow-b
Sync Fathom meeting data to CRM and build automated follow-up workflows. Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs, or creating automated post-meeting email summaries. Trigger with phrases like "fathom crm sync", "fathom salesforce", "fathom follow-up", "fathom post-meeting workflow".
> fathom-core-workflow-a
Build a meeting analytics pipeline with Fathom transcripts and summaries. Use when extracting insights from meetings, building CRM sync, or creating automated meeting follow-up workflows. Trigger with phrases like "fathom analytics", "fathom meeting pipeline", "fathom transcript analysis", "fathom action items sync".
> fathom-common-errors
Diagnose and fix Fathom API errors including auth failures and missing data. Use when API calls fail, transcripts are empty, or webhooks are not firing. Trigger with phrases like "fathom error", "fathom not working", "fathom api failure", "fix fathom".