Brief customer signals from Slack
Connect Slack with read-only public-channel scopes and prepare a weekly customer-signal brief.
The Slack customer signal brief template distills a week of public-channel
conversation into grouped customer pain points, feature requests, praise, and
unresolved questions. It follows the customer-research marketing skill:
quote short representative evidence, never invent sentiment, and end with the
follow-ups most worth human attention.
Enable and connect Slack
Slack's managed MCP server offers no dynamic client registration, so an
operator must configure SLACK_MCP_OAUTH_CLIENT_ID and
SLACK_MCP_OAUTH_CLIENT_SECRET before enabling MANAGED_MCP_SLACK_ENABLED.
Then connect the Slack card from the Connections page and authorize with your
own workspace account.
Work on Repeat requests only channels:read, channels:history,
users:read, and search:read.public — read-level user scopes bounded to
public channels. No chat:*, write, or admin scope is requested, so the
connection cannot post, edit, or react. Access never exceeds what your own
Slack role allows, and a workspace admin can restrict or revoke the app.
Current beta boundary
Slack is connection-only until exact authenticated tool schemas are captured and reviewed. The checked-in policy exposes no runnable tools yet, so the packaged routine ships as a preview. After review, the first manifest should stay read-only.
Recovery and workspace limits
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.
Slack rate-limits conversation history per app and per workspace plan, so
keep the reviewed channel list short and the window to one week.