How do I install the Slack Messaging skill?

Run npx skillmds@latest add boisenoise/slack-messaging in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Slack Messaging safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Slack Messaging?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Slack Messaging free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Slack Messaging?

boisenoise (@boisenoise) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Slack Messaging by boisenoise — Agent Skill

Name: Slack Messaging
Rating: 4.2 (5 reviews)
Author: boisenoise

File contents

Slack Messaging via slackcli

Send and read Slack messages from the command line using slackcli (shaharia-lab/slackcli).

Installation

Download the binary:

curl -sL -o /usr/local/bin/slackcli \
  "https://github.com/shaharia-lab/slackcli/releases/download/v0.1.1/slackcli-linux"
chmod +x /usr/local/bin/slackcli

macOS (Intel): replace slackcli-linux with slackcli-macos macOS (Apple Silicon): replace with slackcli-macos-arm64

Authentication

slackcli uses browser session tokens (xoxc + xoxd) - no Slack app creation required.

Interactive Setup

./scripts/extract-tokens <workspace-url>

This walks the user through extracting tokens from browser DevTools.

Manual Setup

slackcli auth login-browser \
  --xoxd="xoxd-..." \
  --xoxc="xoxc-..." \
  --workspace-url=https://your-workspace.slack.com

Verify Auth

slackcli auth list

Finding Channels

Use slackcli conversations list to discover channels and their IDs:

# List all channels
slackcli conversations list

# Filter output
slackcli conversations list | grep -i "channel-name"

Sending Messages

# Send to a channel (use channel ID from conversations list)
slackcli messages send --recipient-id=C0XXXXXXXX --message="Hello from CLI"

# Send to a DM (use user's DM channel ID)
slackcli messages send --recipient-id=D0XXXXXXXX --message="Hey"

# Reply in a thread
slackcli messages send --recipient-id=C0XXXXXXXX --message="Thread reply" --thread-ts=1769756026.624319

The --recipient-id is always a channel ID (C...) or DM channel ID (D...).

Reading Messages

# Read last N messages from a channel
slackcli conversations read C0XXXXXXXX --limit=10

# Read as JSON (for parsing)
slackcli conversations read C0XXXXXXXX --limit=10 --json

# Read a thread
slackcli conversations read C0XXXXXXXX --thread-ts=1769756026.624319

Listing Channels

slackcli conversations list

Returns all public channels, private channels, and DMs with their IDs.

Testing Slack Integrations

To verify a bot or integration posted a message correctly:

# Read the channel, check for the expected message
slackcli conversations read CHANNEL_ID --limit=5 --json | jq '.messages[] | select(.text | contains("expected text"))'

To send a test message and verify the round-trip:

# Send
slackcli messages send --recipient-id=CHANNEL_ID --message="integration test $(date +%s)"

# Read back
slackcli conversations read CHANNEL_ID --limit=1 --json

Multiple Workspaces

slackcli supports multiple workspaces. Run the auth flow for each workspace you need:

# Add first workspace
./scripts/extract-tokens https://workspace-one.slack.com

# Add second workspace
./scripts/extract-tokens https://workspace-two.slack.com

# List all authenticated workspaces
slackcli auth list

When sending messages, slackcli automatically routes to the correct workspace based on the channel ID.

Token Notes

Browser tokens (xoxc/xoxd) act as the logged-in user, not a bot
Messages sent appear as the user, not an app
Tokens expire when the user logs out of the browser session
To refresh: re-extract tokens from a logged-in browser session
All workspace credentials are stored at ~/.config/slackcli/workspaces.json

---name: slack-messagingdescription: Use when asked to send or read Slack messages, check Slack channels, test Slack integrations, or interact with a Slack workspace from the command line.---# Slack Messaging via slackcliSend and read Slack messages from the command line using `slackcli` (shaharia-lab/slackcli).## InstallationDownload the binary:```bashcurl -sL -o /usr/local/bin/slackcli \ "https://github.com/shaharia-lab/slackcli/releases/download/v0.1.1/slackcli-linux"chmod +x /usr/local/bin/slackcli```macOS (Intel): replace `slackcli-linux` with `slackcli-macos`macOS (Apple Silicon): replace with `slackcli-macos-arm64`## Authenticationslackcli uses browser session tokens (xoxc + xoxd) - no Slack app creation required.### Interactive Setup```bash./scripts/extract-tokens <workspace-url>```This walks the user through extracting tokens from browser DevTools.### Manual Setup```bashslackcli auth login-browser \ --xoxd="xoxd-..." \ --xoxc="xoxc-..." \ --workspace-url=https://your-workspace.slack.com```### Verify Auth```bashslackcli auth list```## Finding ChannelsUse `slackcli conversations list` to discover channels and their IDs:```bash# List all channelsslackcli conversations list# Filter outputslackcli conversations list | grep -i "channel-name"```## Sending Messages```bash# Send to a channel (use channel ID from conversations list)slackcli messages send --recipient-id=C0XXXXXXXX --message="Hello from CLI"# Send to a DM (use user's DM channel ID)slackcli messages send --recipient-id=D0XXXXXXXX --message="Hey"# Reply in a threadslackcli messages send --recipient-id=C0XXXXXXXX --message="Thread reply" --thread-ts=1769756026.624319```The `--recipient-id` is always a channel ID (C...) or DM channel ID (D...).## Reading Messages```bash# Read last N messages from a channelslackcli conversations read C0XXXXXXXX --limit=10# Read as JSON (for parsing)slackcli conversations read C0XXXXXXXX --limit=10 --json# Read a threadslackcli conversations read C0XXXXXXXX --thread-ts=1769756026.624319```## Listing Channels```bashslackcli conversations list```Returns all public channels, private channels, and DMs with their IDs.## Testing Slack IntegrationsTo verify a bot or integration posted a message correctly:```bash# Read the channel, check for the expected messageslackcli conversations read CHANNEL_ID --limit=5 --json | jq '.messages[] | select(.text | contains("expected text"))'```To send a test message and verify the round-trip:```bash# Sendslackcli messages send --recipient-id=CHANNEL_ID --message="integration test $(date +%s)"# Read backslackcli conversations read CHANNEL_ID --limit=1 --json```## Multiple Workspacesslackcli supports multiple workspaces. Run the auth flow for each workspace you need:```bash# Add first workspace./scripts/extract-tokens https://workspace-one.slack.com# Add second workspace./scripts/extract-tokens https://workspace-two.slack.com# List all authenticated workspacesslackcli auth list```When sending messages, slackcli automatically routes to the correct workspace based on the channel ID.## Token Notes- Browser tokens (xoxc/xoxd) act as the logged-in user, not a bot- Messages sent appear as the user, not an app- Tokens expire when the user logs out of the browser session- To refresh: re-extract tokens from a logged-in browser session- All workspace credentials are stored at `~/.config/slackcli/workspaces.json`

Frequently asked questions

Slack Messaging