Slack
Read-only Slack through your own account. A pulse across your channels, the replies you owe, threads where someone outside the workspace is waiting, and channels you joined that the agent doesn't know about yet. It never posts and never reads DMs.
The Slack pack lets the agent read the Slack channels your own account is in. Ask in plain words: "slack pulse", "what's happening in ext-acme today", "pull this thread <link>", "search Slack for INV-1042".
It reads and never writes. The token has no scope to post, react or open a DM, and the agent refuses a token that has one.
What it gives you
- A pulse across your channels, grouped by a channel map you own, and direct reads of one channel, a thread or a search.
- What's waiting: the replies you owe, external threads waiting on your team, and channels you joined that the map doesn't list. The attention queue and sync show them.
What it needs
- A Slack app in your workspace, created once. Anyone allowed to create apps there can do it, and teammates who join later reuse its Client ID.
- Your own sign-in. The agent sees only the channels your account can see.
- Cost: free.
Switch it on
Run configure-skills and pick Slack. The walk has three parts.
A Slack app for your workspace, once
If your workspace already has the app, paste its Client ID and skip ahead. If not, the walk takes you through it:
- At api.slack.com/apps, choose Create New App → From scratch, name it after your agent and pick your workspace.
- Under OAuth & Permissions → User Token Scopes (not Bot Token Scopes), add
channels:history,channels:read,groups:history,groups:read,users:readandsearch:read. Nothing else. - Add
http://localhostunder Redirect URLs. - Turn on Advanced token security via PKCE. Slack says this can't be undone. It's what lets the agent sign in without a client secret.
- Copy the Client ID from Basic Information and paste it into the walk. It's a public identifier, not a secret, and it's saved as
AGENT_SLACK_CLIENT_IDin<HOME>/.claude/settings.local.json. - If your workspace requires admin approval, install the app and have an admin approve it once.
Your own sign-in, once
The sign-in waits for Slack's answer on a local port, which the agent's sandbox doesn't allow, so you run it in your own terminal. The walk prints the exact command with your paths filled in:
cd <HOME> && bun "<plugin root>/src/cli.ts" slack authYour browser opens Slack's authorize page. Click Allow, and the terminal prints {"ok": true, …}. The tokens land in <HOME>/.state/secrets/slack/slack-tokens.json, readable only by you, under the secrets folder the agent's own shell can't read. The Slack tools run in the agent's MCP server, which can.
A first channel map
The walk then writes knowledge/concepts/slack-channels.md from the channels you're in, unless you already have one. The channel map explains the file.
A refresh token expires after 30 days without use. If that happens, run the same slack auth command again.
The channel map
The agent groups your channels in a markdown file you own, knowledge/concepts/slack-channels.md:
## Team
- team-eng
- team-ops — on-call and deploys
## External
- ext-acme — Acme Corp, shared channel
- ext-globex
## Reference (opt-in)
- general
## Uncategorized
- ext-initech — joined 2026-01-15The rules below say what each category means and how the agent files a channel it hasn't seen.
What's waiting
The slack_waiting tool decides in code what's waiting, and returns who, where, how long and a link, never message text. That's what lets an unattended sync run it.
It returns three lists: the replies you owe, external threads waiting on your team, and new channels.
The attention queue shows the first two as groups, each item with how long it has waited. New channels show as a note under External threads waiting. Sync prints all three in a 🔔 Slack block, and its closing questions offer slack sort new channels, which files each new channel into the map without reading any messages.
A pulse
slack with no argument scans every categorised channel except Reference for the last 24 hours, in one batched read. It drops acknowledgements and routine bot posts, and keeps unanswered questions, errors, asks, decisions and blockers. The brief is grouped by category, most urgent first, and saved to reports/slack/. slack external scans one category. A single channel, a thread or a search is answered directly and isn't saved unless you ask.
The brief quotes at most one line of any message, and the agent never drafts a reply to send. Every read is logged under [💬 slack] in .state/logs/app.log.
Turning it off
Run configure-skills, choose Deconfigure a skill pack, then Slack. It revokes the tools and offers the command that deletes your local token. To revoke the app's access on Slack's side, open your workspace's Authorized apps settings and revoke it there. Your teammates' tokens are their own and keep working.
Where it's used
The attention queue, sync and the dashboard's Today tab show what Slack is waiting on.
SEO
Search Console, PageSpeed, SerpAPI and Open Page Rank behind one read-only seo skill, plus wordpress-rest for site content.
Helpdesk
Your support queue in SupportCandy or Pylon, worked the way your team works it. The agent reads, sorts and drafts; a person sends every reply. A queue profile per project holds its own pulse, bug lifecycle, routines and context.