OpenWork in Slack, private alpha

Guides: https://openworklabs.com/docs/slack/set-up-the-slack-app.md (administrator setup) and https://openworklabs.com/docs/slack/connect-your-account.md (member linking and verification)

Use browser/computer tools for the existing signed-in OpenWork and Slack administration sessions. Prefer supported setup tools if available. This skill does not grant alpha access or authorize actions beyond the user's request and your tools' permissions.

Establish the target

Identify the OpenWork organization, Slack workspace, existing Slack app, and connector. Do not create duplicates. In Connectors → Slack → OpenWork in Slack, check eligibility, platform rollout access, runtime access, installation, enabled state, signing-secret presence, and channel/reply settings. If alpha or runtime access is missing, report the exact missing prerequisite; do not change deployment settings unless requested.

Ask for the user's channel scope if unspecified: selected channel IDs or all channels. Blank channel IDs allows all channels but does not invite the bot. Private replies are a useful rollout default; honor the user's choice.

Configure the existing app

Read the generated manifest from this connector, then read the current manifest in that same Slack app. Merge without removing existing user scopes, optional user scopes, redirects, MCP configuration, or unrelated features. Keep a before/after comparison in memory. Never replace the entire manifest with only the generated fragment.

Required bot scopes: app_mentions:read, chat:write, im:history, im:read, im:write, assistant:write, commands. Required events: app_mention, message.im, app_home_opened, app_context_changed, agent_session_stopped, agent_session_title_changed, app_uninstalled, tokens_revoked.