Slack Bot (slack.com). Use this skill for ANY Slack Bot request — reading, creating, updating, and deleting data. Whenever a task involves Slack Bot, use this skill instead of calling the API directly.
Pro shows the line behind each finding and how to fix it
Scanned 9/24/2026
npx -y skills add oomol-lab/skills --skill oo-slackbot --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Oo Slackbot?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oomol-lab-oo-slackbot)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: oo-slackbot
description: "Slack Bot (slack.com). Use this skill for ANY Slack Bot request — reading, creating, updating, and deleting data. Whenever a task involves Slack Bot, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
title: "Slack Bot"
author: "OOMOL"
version: "1.0.4"
services: ["slackbot"]
icon: "https://static.oomol.com/logo/third-party/slackbot.svg"
---
# Slack Bot
Operate **Slack Bot** through your OOMOL-connected account. This skill calls the `slackbot` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.
## Running an action
Assume the user has already installed the oo CLI, signed in, and connected Slack Bot. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.
**1. Inspect the contract** to get the authoritative input/output schema before building a payload:
```bash
oo connector schema "slackbot" --action "<action_name>"
```
**2. Run the action** with a JSON payload that matches the input schema:
```bash
oo connector run "slackbot" --action "<action_name>" --data '<json>' --json
```
- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.
Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.
### Preserve multiline message text
Slack renders real newline characters in `text`; it renders literal backslash-n
characters as `\n`. Keep one JSON-encoding boundary:
- Before serialization, message text must contain actual LF characters.
- In serialized JSON, each intended newline appears as `\n`. If it appears as
`\\n`, it has been double-escaped and Slack will display `\n`.
- When passing raw JSON to `--data`, write the JSON newline escape exactly once.
```bash
oo connector run "slackbot" \
--action "post_message" \
--data '{"channelId":"C123","text":"First paragraph.\n\nSecond paragraph."}' \
--json
```
If visible formatting matters, read the posted message back and confirm that
`text` contains line breaks rather than literal `\n` characters.
## Available actions
- `add_reaction` — Add an emoji reaction to a Slack message. [write]
- `conversations_members` — List one page of member user IDs for a Slack conversation.
- `delete_file` — Delete a Slack file. [destructive]
- `delete_message` — Delete a Slack message posted through this connection. [destructive]
- `download_file` — Download a Slack-hosted file into Connector file transit storage using the connected identity's access.
- `get_channel_messages` — Get recent messages from a Slack conversation.
- `get_conversation` — Get metadata for a Slack conversation.
- `get_current_user` — Get the workspace and user identity of the connected Slack credential.
- `get_file` — Get metadata for a Slack file.
- `get_message_permalink` — Get a permalink for a Slack message.
- `get_reactions` — Get reactions for a Slack message.
- `get_thread` — Get messages in a Slack thread.
- `get_user` — Get metadata for a Slack user.
- `list_channels` — List Slack public channels visible to the connected Slack identity.
- `list_conversations` — List Slack conversations visible to the connected Slack identity.
- `list_files` — List Slack files visible to the connected Slack identity, optionally filtered by channel or user.
- `list_users` — List Slack users visible to the connected Slack identity.
- `open_conversation` — Open or resume a direct message with one Slack user. [write]
- `post_ephemeral_message` — Post an ephemeral Slack message visible only to one user in a conversation. [write]
- `post_message` — Post a Slack message. Use text for plain messages, or blocks for rich Block Kit layouts with text as fallback. [write]
- `remove_reaction` — Remove an emoji reaction from a Slack message. [destructive]
- `reply_message` — Reply to a Slack thread. Use text, blocks, or attachments for the reply content. [write]
- `schedule_message` — Schedule a Slack message to be posted later. Use text or blocks for the scheduled content. [write]
- `update_message` — Update a Slack message posted through this connection. Provide text, blocks, or attachments as the new message content. [write]
- `upload_file` — Upload a file to Slack using the current external upload flow. Provide fileUrl; binary content is fetched by the connector runtime. [write]
## Safety
- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change Slack Bot state — confirm the exact payload and effect with the user before running.**
- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**
## First-time setup
These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):
```bash
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
```
```powershell
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
```
- **Not signed in / authentication error** — sign in to your OOMOL account once:
```bash
oo auth login
```
- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Slack Bot is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:
```text
https://console.oomol.com/app-connections?provider=slackbot
```
- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
## Resources
- Slack Bot homepage: https://slack.com
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!