configure
Configure Slack channel tokens (bot token + app-level token)
Best use case
configure is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure Slack channel tokens (bot token + app-level token)
Teams using configure should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/configure/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How configure Compares
| Feature / Agent | configure | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure Slack channel tokens (bot token + app-level token)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# /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](https://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
1. 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)
2. 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-...
```
3. Create the state directory if it doesn't exist:
```
~/.claude/channels/slack/
```
4. Write the `.env` file at `~/.claude/channels/slack/.env`:
```
SLACK_BOT_TOKEN=<bot-token>
SLACK_APP_TOKEN=<app-token>
```
5. Set file permissions to owner-only:
```bash
chmod 600 ~/.claude/channels/slack/.env
```
6. 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 `.env` file
## 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](https://api.slack.com/start/quickstart) — app setup walkthrough
- [Slack Socket Mode](https://api.slack.com/apis/socket-mode) — how to enable and get app-level tokens
- Access control: `/slack-channel:access` — configure who can message your sessionRelated Skills
schema-optimization-orchestrator
Multi-phase schema optimization workflow orchestrator. Creates session directories, spawns phase agents sequentially, validates outputs, aggregates results. Trigger: "run schema optimization", "optimize schema workflow", "execute schema phases"
test-skill
Test skill for E2E validation. Trigger with "run test skill" or "execute test". Use this skill when testing skill activation and tool permissions.
example-skill
Brief description of what this skill does and when the model should activate it. Use when [describe the user's intent or situation]. Trigger with "example phrase", "another trigger", "/example-skill".
testing-visual-regression
Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".
generating-unit-tests
Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".
generating-test-reports
Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".
orchestrating-test-execution
Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".
managing-test-environments
Test provision and manage isolated test environments with configuration and data. Use when performing specialized testing. Trigger with phrases like "manage test environment", "provision test env", or "setup test infrastructure".
generating-test-doubles
Generate mocks, stubs, spies, and fakes for dependency isolation. Use when creating mocks, stubs, or test isolation fixtures. Trigger with phrases like "generate mocks", "create test doubles", or "setup stubs".
generating-test-data
Generate realistic test data including edge cases and boundary conditions. Use when creating realistic fixtures or edge case test data. Trigger with phrases like "generate test data", "create fixtures", or "setup test database".
analyzing-test-coverage
Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
managing-snapshot-tests
Create and validate component snapshots for UI regression testing. Use when performing specialized testing. Trigger with phrases like "update snapshots", "test UI snapshots", or "validate component snapshots".