Agent skill · security · jeremylongshore
configure
Configure Slack channel tokens (bot token + app-level token). Use when writing or rotating the Slack bot and app-level tokens for the slack-channel plugin. Trigger with "/slack-channel:configure", "configure slack tokens", or "set up my slack bot token".
Why this skill is useful
Adds a specific configuration workflow for Slack tokens that includes validation and secure storage practices not commonly known.
What it needs
Requires bash installed locally. Requires slack account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
/slack-channel:configure Overview Configure the Slack channel with your bot token and app-level token. This is the single place tokens touch disk: the skill validates both token prefixes, writes them to the state directory's .env, and locks the file to owner-only permissions. It never echoes tokens back. The install walkthrough (/slack-channel:install Step 3) delegates here. Prerequisites A Slack app already created (via /slack-channel:install Step 1 or manually at api.slack.com/apps) with: the Bot User OAuth Token (xoxb-...) from OAuth & Permissions, and the App-Level Token (xapp-..., scope connections:write) from Socket Mode settings. A writable home directory — state lives at ~/.claude/channels/slack/. Usage Pass both tokens as arguments, bot token first: 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: 3. Create the state directory if it doesn't exist: 4. Write the .env file at ~/.claude/channels/slack/.env: 5. Set file permissions to owner-only: 6. Confirm success: Output On success: ~/.claude/channels/slack/.env written with both tokens and mode 0600, plus the confirmation block above (server start command and the pointer to channel opt-in). Tokens are never echoed. On failure: the two-token usage error from step 2 and no file changes. Error Handling Missing token or wrong prefix — show the step-2 error block and stop; nothing is written. Bot tokens must start with xoxb-, app tokens with xapp-. Tokens swapped — the prefix check catches it; re-run with the bot token first. Existing .env — re-running overwrites it in place; this is the supported token-rotation path (Slack tokens are reusable; rotation happens at api.slack.com/apps). Revoked/invalid tokens — this skill only validates prefixes, not liveness. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/configure