agentleFS
alanalvestechalanalvestech/hitank/skills/slack/SKILL.md

slack

Skill38 starsChanged 8 months agoMITView on GitHub

Manage Slack channels, messages, users, reactions and files via Bot API

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, BlueBubbles and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • jiulingyunSkill

    BlueBubbles

    为Clawdbot构建或更新BlueBubbles外部通道插件(扩展包,REST发送/探测,webhook入站)。

    Also in 18 projects that use this

  • seedprodSkill

    voice-call

    Start voice calls via the OpenClaw voice-call plugin.

    Also in 16 projects that use this

  • hkyutongSkill

    openclaw-release-maintainer

    Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

    Also in 4 projects that use this

  • seedprodSkill

    session-logs

    Search and analyze your own session logs (older/parent conversations) using jq.

    Also in 16 projects that use this

  • AtomicBot-aiSkill

    taskflow

    Also in 6 projects that use this

  • +5 more from seedprod

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If the output is OK, proceed to the Flow section.

    line 39
  2. Very specific:

    If the output is SETUP_NEEDED, guide the user step by step.

    line 41
  3. Distinctive:

    If the script outputs an error, the token is invalid.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “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

Connect to Slack to manage channels, send messages, browse history, list users, add reactions, pin messages, upload files and search across your workspace. Pure Ruby, zero gems — stdlib only.

Structure

scripts/
├── auth.rb            # Bearer token auth + slack_request helper (required by all scripts)
├── check_setup.rb     # Check if token exists (outputs OK or SETUP_NEEDED)
├── save_token.rb      # Save and validate a Bot token
├── channels.rb        # List channels in the workspace
├── channel_info.rb    # Get info about a channel
├── post_message.rb    # Post a message to a channel
├── messages.rb        # Get message history for a channel
├── users.rb           # List users in the workspace
├── user_info.rb       # Get info about a user
├── add_reaction.rb    # Add a reaction to a message
├── remove_reaction.rb # Remove a reaction from a message
├── pins.rb            # List pinned messages in a channel
├── pin_message.rb     # Pin a message in a channel
├── upload_file.rb     # Upload file content to a channel
└── search_messages.rb # Search messages across the workspace

Setup (check before using)

ruby ~/.claude/skills/slack/scripts/check_setup.rb

If the output is OK, proceed to the Flow section.

If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.

Step 1 — Ask the user to create a Slack app and get the Bot token:

You need a Slack Bot User OAuth Token. Go to the Slack API portal: https://api.slack.com/apps

  1. Click Create New App > From scratch, give it a name and select your workspace
  2. Go to OAuth & Permissions in the left menu
  3. Under Bot Token Scopes, add the following scopes:
    • channels:read
    • channels:history
    • chat:write
    • users:read
    • reactions:write
    • pins:write
    • files:write
    • search:read
  4. Click Install to Workspace at the top and authorize
  5. Copy the Bot User OAuth Token (starts with xoxb-)

Paste the bot token here.

Step 2 — When the user pastes the token, save it:

ruby ~/.claude/skills/slack/scripts/save_token.rb 'PASTED_TOKEN'

If the script outputs an error, the token is invalid. Ask the user to double-check and try again.

If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.

Flow

The argument $ARGUMENTS may contain a channel name or action reference.

Step 1: List channels

ruby ~/.claude/skills/slack/scripts/channels.rb
ruby ~/.claude/skills/slack/scripts/channels.rb --limit 50
ruby ~/.claude/skills/slack/scripts/channels.rb --types public_channel,private_channel

Present the channels. Ask which channel to work with if needed.

Step 2: Actions

Get channel info:

ruby ~/.claude/skills/slack/scripts/channel_info.rb CHANNEL_ID

Read messages:

ruby ~/.claude/skills/slack/scripts/messages.rb CHANNEL_ID
ruby ~/.claude/skills/slack/scripts/messages.rb CHANNEL_ID --limit 50

Post a message (requires user confirmation):

Show the message content first, then ask to confirm before sending.

ruby ~/.claude/skills/slack/scripts/post_message.rb CHANNEL_ID "Hello from HiTank!"

List users:

ruby ~/.claude/skills/slack/scripts/users.rb
ruby ~/.claude/skills/slack/scripts/users.rb --limit 50

Get user info:

ruby ~/.claude/skills/slack/scripts/user_info.rb USER_ID

Add a reaction (requires user confirmation):

ruby ~/.claude/skills/slack/scripts/add_reaction.rb CHANNEL_ID TIMESTAMP thumbsup

Remove a reaction (requires user confirmation):

ruby ~/.claude/skills/slack/scripts/remove_reaction.rb CHANNEL_ID TIMESTAMP thumbsup

List pinned messages:

ruby ~/.claude/skills/slack/scripts/pins.rb CHANNEL_ID

Pin a message (requires user confirmation):

ruby ~/.claude/skills/slack/scripts/pin_message.rb CHANNEL_ID TIMESTAMP

Upload a file (requires user confirmation):

ruby ~/.claude/skills/slack/scripts/upload_file.rb CHANNEL_ID "file content here" --filename notes.txt --title "My Notes"

Search messages:

ruby ~/.claude/skills/slack/scripts/search_messages.rb "search query"
ruby ~/.claude/skills/slack/scripts/search_messages.rb "search query" --count 10

Notes

  • Pure Ruby, zero gems — stdlib only (json, net/http, uri, fileutils)
  • Auth via Bot User OAuth Token (Authorization: Bearer xoxb-...)
  • Token file: ~/.config/slack/token (outside the repo, never commit)
  • Posting messages, adding/removing reactions, pinning, and uploading files require explicit user confirmation
  • Mention users as <@USER_ID> in message content
  • Slack API returns {"ok": true/false} — all scripts check data['ok'] and output errors
  • The search:read scope is required for search_messages.rb
  • Base URL: https://slack.com/api

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.