agentleFS
claude-worldclaude-world/claude-agent/.claude/skills/slack-ops/SKILL.md

slack-ops

Skill5 starsChanged 8 months agoMITView on GitHub

Operate Slack via the Web API using curl and a SLACK_TOKEN env var. Send messages, add reactions, pin messages, and list channels. Use when user says "post to Slack", "send Slack message", "react to message", "pin in Slack", or "list Slack channels".

  • Sends data out

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No CLI install needed — uses curl (pre-installed on macOS/Linux).

    line 28
  2. Very specific:

    Always check that SLACK_TOKEN is set before running any command: [[ -z "$SLACK_TOKEN" ]] && echo "SLACK_TOKEN not set"

    line 99
  3. Distinctive:

    If token is missing, instruct user to set it and stop

    line 100
  4. Distinctive:

    Never print the token value in output

    line 101
  5. Very specific:

    Always parse API responses with jq and check "ok": true.

    line 102
  6. Distinctive:

    Keep messages concise; for long content, consider posting a summary with a workspace file link

    line 105

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Slack Ops

Interact with Slack via the official Web API using curl. Requires a SLACK_TOKEN environment variable (Bot Token starting with xoxb-).

Prerequisites

No CLI install needed — uses curl (pre-installed on macOS/Linux).

Set up your bot token:

export SLACK_TOKEN="xoxb-your-token-here"
# Or add to ~/.zshrc / ~/.bashrc for persistence

To get a token: https://api.slack.com/apps → Create App → OAuth & Permissions → add scopes (chat:write, channels:read, reactions:write, pins:write) → Install to Workspace → copy Bot User OAuth Token.

Commands

Send a message:

curl -s -X POST https://slack.com/api/chat.postMessage \
  -H "Authorization: Bearer $SLACK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channel": "#general", "text": "Hello team!"}'

Send with blocks (rich text):

curl -s -X POST https://slack.com/api/chat.postMessage \
  -H "Authorization: Bearer $SLACK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channel": "#general", "blocks": [{"type":"section","text":{"type":"mrkdwn","text":"*Update*: Build passed."}}]}'

Add a reaction:

# Requires channel ID, message timestamp
curl -s -X POST https://slack.com/api/reactions.add \
  -H "Authorization: Bearer $SLACK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channel": "C12345678", "name": "white_check_mark", "timestamp": "1609459200.000100"}'

Pin a message:

curl -s -X POST https://slack.com/api/pins.add \
  -H "Authorization: Bearer $SLACK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channel": "C12345678", "timestamp": "1609459200.000100"}'

List channels:

curl -s "https://slack.com/api/conversations.list?limit=50" \
  -H "Authorization: Bearer $SLACK_TOKEN" | jq '.channels[] | {id, name}'

Get channel history:

curl -s "https://slack.com/api/conversations.history?channel=C12345678&limit=20" \
  -H "Authorization: Bearer $SLACK_TOKEN" | jq '.messages[] | {ts, text, user}'

Usage Examples

Post a quick status update:

curl -s -X POST https://slack.com/api/chat.postMessage \
  -H "Authorization: Bearer $SLACK_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"channel": "#deploys", "text": "v2.1.0 deployed to production."}'

Rules

  • Always check that SLACK_TOKEN is set before running any command: [[ -z "$SLACK_TOKEN" ]] && echo "SLACK_TOKEN not set"
  • If token is missing, instruct user to set it and stop
  • Never print the token value in output
  • Always parse API responses with jq and check "ok": true; if "ok": false, show the error field
  • Channel names use #name format for posting; channel IDs (C...) are required for reactions/pins — run channels.list first if needed
  • Confirm message sends with: "Posted to #<channel>"
  • Keep messages concise; for long content, consider posting a summary with a workspace file link

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.