Slack
Let your coding agent read and act on Slack channels, messages, and users through Membrane’s CLI instead of hand-rolling OAuth and token refresh.
Overview
Slack is an agent skill for the Build phase that connects your agent to Slack channels, messages, and users through the Membrane CLI and managed auth.
Install
npx skills add https://github.com/membranedev/application-skills --skill slackWhat is this skill?
- Slack integration via Membrane CLI with automatic credential refresh
- Entity model covers channels, messages, and users per Slack Web API
- Install path: npm install -g @membranehq/cli@latest
- membrane login --tenant --clientName for browser or headless auth flows
- MIT-licensed application skill from membranedev/application-skills
- Membrane CLI install via @membranehq/cli@latest
- Skill metadata version 1.0
Adoption & trust: 530 installs on skills.sh; 178 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want the agent to use Slack in a workflow but raw API tokens, OAuth, and refresh logic block you from shipping the integration.
Who is it for?
Solo builders already using Membrane who need Slack reads/writes inside agent-driven internal tools or ops bots.
Skip if: Teams that cannot allow network access, Membrane accounts, or global npm CLI installs in the agent sandbox.
When should I use this skill?
Use when the user wants to interact with Slack data or manage Slack communication records and workflows.
What do I get? / Deliverables
After setup, the agent can call Membrane-mediated Slack actions with authenticated sessions so you can focus on the automation logic.
- Authenticated Slack API operations via Membrane
- Agent-run Slack channel/message/user workflows
Recommended Skills
Journey fit
Build / integrations is the canonical shelf because the skill’s job is wiring Slack into agent workflows via Membrane, not distribution or production monitoring. Integrations matches third-party SaaS connectivity (Slack API actions) with auth handled by Membrane.
How it compares
Skill package for Slack via Membrane—not a self-hosted Slack MCP server and not Slack’s Block Kit UI builder.
Common Questions / FAQ
Who is slack for?
Indie developers and small teams building agent automations that need authenticated Slack API access without custom OAuth code.
When should I use slack?
Use it during Build integrations when the user asks to interact with Slack data, sync comms into another system, or automate channel and message workflows.
Is slack safe to install?
It requires network access, CLI install, and third-party auth; review the Security Audits panel on this page and scope Membrane/Slack tokens to least privilege.
SKILL.md
READMESKILL.md - Slack
# Slack Slack is a messaging app for businesses that connects people to the information they need. It's used by teams of all sizes to communicate, collaborate, and share files in a central workspace. Official docs: https://api.slack.com/ ## Slack Overview - **Channel** - **Message** - **User** Use action names and parameters as needed. ## Working with Slack This skill uses the Membrane CLI to interact with Slack. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing. ### Install the CLI Install the Membrane CLI so you can run `membrane` from the terminal: ```bash npm install -g @membranehq/cli@latest ``` ### Authentication ```bash membrane login --tenant --clientName=<agentType> ``` This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available. **Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with: ```bash membrane login complete <code> ``` Add `--json` to any command for machine-readable JSON output. **Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness ### Connecting to Slack Use `membrane connection ensure` to find or create a connection by app URL or domain: ```bash membrane connection ensure "https://slack.com" --json ``` The user completes authentication in the browser. The output contains the new connection id. This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically. If the returned connection has `state: "READY"`, skip to **Step 2**. #### 1b. Wait for the connection to be ready If the connection is in `BUILDING` state, poll until it's ready: ```bash npx @membranehq/cli connection get <id> --wait --json ``` The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`. The resulting state tells you what to do next: - **`READY`** — connection is fully set up. Skip to **Step 2**. - **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action: - `clientAction.type` — the kind of action needed: - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections. - `"provide-input"` — more information is needed (e.g. which app to connect to). - `clientAction.description` — human-readable explanation of what's needed. - `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present. - `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically. After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`. - **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details. ### Searching for actions Search using a natural language description of what you want to do: ```bash membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json ``` You sho