Menu
Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | slack-automation |
| description | Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit. |
| risk | critical |
| source | community |
| date_added | 2026-02-27 |
Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.
RUBE_MANAGE_CONNECTIONS with toolkit slackRUBE_SEARCH_TOOLS first to get current tool schemasGet Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit slackWhen to use: User wants to post a message to a Slack channel or DM
Tool sequence:
SLACK_FIND_CHANNELS - Resolve channel name to channel ID [Prerequisite]SLACK_LIST_ALL_CHANNELS - Fallback if FIND_CHANNELS returns empty/ambiguous results [Fallback]SLACK_FIND_USERS - Resolve user for DMs or @mentions [Optional]SLACK_OPEN_DM - Open/reuse a DM channel if messaging a user directly [Optional]SLACK_SEND_MESSAGE - Post the message with resolved channel ID [Required]SLACK_UPDATES_A_SLACK_MESSAGE - Edit the posted message if corrections needed [Optional]Key parameters:
channel: Channel ID or name (without '#' prefix)markdown_text: Preferred field for formatted messages (supports headers, bold, italic, code blocks)text: Raw text fallback (deprecated in favor of markdown_text)thread_ts: Timestamp of parent message to reply in a threadblocks: Block Kit layout blocks (deprecated, use markdown_text)Pitfalls:
SLACK_FIND_CHANNELS requires query param; missing it errors with "Invalid request data provided"SLACK_SEND_MESSAGE requires valid channel plus one of markdown_text/text/blocks/attachmentsthread_ts is omittedresponse.data.channel and response.data.message.ts from SEND_MESSAGE for edit/thread operationsWhen to use: User wants to find specific messages across the workspace
Tool sequence:
SLACK_FIND_CHANNELS - Resolve channel for scoped search with in:#channel [Optional]SLACK_FIND_USERS - Resolve user for author filter with from:@user [Optional]SLACK_SEARCH_MESSAGES - Run keyword search across accessible conversations [Required]SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION - Expand threads for relevant hits [Required]Key parameters:
query: Search string supporting modifiers (in:#channel, from:@user, before:YYYY-MM-DD, after:YYYY-MM-DD, has:link, has:file)count: Results per page (max 100), or total with auto_paginate=truesort: 'score' (relevance) or 'timestamp' (chronological)sort_dir: 'asc' or 'desc'Pitfalls:
query is missing/emptyok=true can still mean no hits (response.data.messages.total=0)response.data.messages.matches (sometimes also response.data_preview.messages.matches)match.text may be empty/truncated; key info can appear in matches[].attachments[]response.data.has_more=true; paginate via response_metadata.next_cursorWhen to use: User wants to list channels, users, or workspace info
Tool sequence:
SLACK_FETCH_TEAM_INFO - Validate connectivity and get workspace identity [Required]SLACK_LIST_ALL_CHANNELS - Enumerate public channels [Required]SLACK_LIST_CONVERSATIONS - Include private channels and DMs [Optional]SLACK_LIST_ALL_USERS - List workspace members [Required]SLACK_RETRIEVE_CONVERSATION_INFORMATION - Get detailed channel metadata [Optional]SLACK_LIST_USER_GROUPS_FOR_TEAM_WITH_OPTIONS - List user groups [Optional]Key parameters:
cursor: Pagination cursor from response_metadata.next_cursorlimit: Results per page (default varies; set explicitly for large workspaces)types: Channel types filter ('public_channel', 'private_channel', 'im', 'mpim')Pitfalls:
response.data.team, not top-levelSLACK_LIST_ALL_CHANNELS returns public channels only; use SLACK_LIST_CONVERSATIONS for private/IM coverageSLACK_LIST_ALL_USERS can hit HTTP 429 rate limits; honor Retry-After headerresponse_metadata.next_cursor until empty; de-duplicate by idWhen to use: User wants to add reactions or manage threaded conversations
Tool sequence:
SLACK_SEARCH_MESSAGES or SLACK_FETCH_CONVERSATION_HISTORY - Find the target message [Prerequisite]SLACK_ADD_REACTION_TO_AN_ITEM - Add an emoji reaction [Required]SLACK_FETCH_ITEM_REACTIONS - List reactions on a message [Optional]SLACK_REMOVE_REACTION_FROM_ITEM - Remove a reaction [Optional]SLACK_SEND_MESSAGE - Reply in thread using thread_ts [Optional]SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION - Read full thread [Optional]Key parameters:
channel: Channel ID where the message livestimestamp / ts: Message timestamp (unique identifier like '1234567890.123456')name: Emoji name without colons (e.g., 'thumbsup', 'wave::skin-tone-3')thread_ts: Parent message timestamp for threaded repliesPitfalls:
SLACK_FETCH_CONVERSATION_HISTORY only returns main channel timeline, NOT threaded repliesSLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION with parent's thread_ts to get thread repliesWhen to use: User wants to schedule a message for future delivery
Tool sequence:
SLACK_FIND_CHANNELS - Resolve channel ID [Prerequisite]SLACK_SCHEDULE_MESSAGE - Schedule the message with post_at timestamp [Required]Key parameters:
channel: Resolved channel IDpost_at: Unix timestamp for delivery (up to 120 days in advance)text / blocks: Message contentPitfalls:
post_at must be a Unix timestamp, not ISO 8601Always resolve display names to IDs before operations:
SLACK_FIND_CHANNELS with query paramSLACK_FIND_USERS with search_query or emailSLACK_OPEN_DM with resolved user IDsMost list endpoints use cursor-based pagination:
response_metadata.next_cursor until emptylimit values (e.g., 100-200) for reliable pagingid across pagesmarkdown_text over text or blocks for formatted messages<@USER_ID> format to mention users (not @username)\n for line breaks in markdown_textSLACK_FIND_CHANNELS can return empty results if channel is private and bot hasn't been invitedSLACK_LIST_ALL_USERS and other list endpoints can hit HTTP 429; honor Retry-After headerresponse.data.results[0].response.data in wrapped executionsSLACK_FETCH_CONVERSATION_HISTORY returns main timeline only; use SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION for thread replieschannel and original message ts; persist these from SEND_MESSAGE responseSLACK_GET_APP_PERMISSION_SCOPES| Task | Tool Slug | Key Params |
|---|---|---|
| Find channels | SLACK_FIND_CHANNELS | query |
| List all channels | SLACK_LIST_ALL_CHANNELS | limit, cursor, types |
| Send message | SLACK_SEND_MESSAGE | channel, markdown_text |
| Edit message | SLACK_UPDATES_A_SLACK_MESSAGE | channel, ts, markdown_text |
| Search messages | SLACK_SEARCH_MESSAGES | query, count, sort |
| Get thread | SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION | channel, ts |
| Add reaction | SLACK_ADD_REACTION_TO_AN_ITEM | channel, name, timestamp |
| Find users | SLACK_FIND_USERS | search_query or email |
| List users | SLACK_LIST_ALL_USERS | limit, cursor |
| Open DM | SLACK_OPEN_DM | user IDs |
| Schedule message | SLACK_SCHEDULE_MESSAGE | channel, post_at, text |
| Get channel info | SLACK_RETRIEVE_CONVERSATION_INFORMATION | channel ID |
| Channel history | SLACK_FETCH_CONVERSATION_HISTORY | channel, oldest, latest |
| Workspace info | SLACK_FETCH_TEAM_INFO | (none) |
This skill is applicable to execute the workflow or actions described in the overview.
This skill should be used for advanced LLM evaluation: LLM-as-judge systems, direct scoring, pairwise comparison, rubric calibration, evaluator bias mitigation, confidence scoring, and automated quality assessment.
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
This skill should be used when modeling agent mental states with BDI concepts: beliefs, desires, intentions, RDF-to-belief transformations, rational agency traces, cognitive agents, BDI ontologies, and neuro-symbolic AI integration.
Build a premium cinematic landing page with mouse-scrub video hero and brand-driven narrative-arc sections. Use whenever the user provides a hero video plus a product / subject / brand and wants a landing page, promo site, product showcase, marketing page, or storytelling site. Works for any language and any subject. The signature effect is mouse-driven video scrubbing — the hero video lives across the entire page as a fixed backdrop, and moving the mouse left-right scrubs the video timeline so the subject responds to the cursor. Below the hero, 4-5 fully-opaque sections each carry their own brand identity (color, typography emphasis, layout pattern) and walk the viewer through a narrative arc (e.g. longing -> joy -> nostalgia -> contemplation -> action). Do NOT use for parallax frame-scrub landings where the page itself doesn't scroll (use parallax-landing-page instead) or for video editing / captioning workflows (use video-edit).
Convert frontend code (Vite, React, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. **ALWAYS** use this skill when the user's intent is to move existing web apps or React components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked.
This skill should be used for diagnosing and mitigating context degradation: lost-in-middle failures, context poisoning, context clash, context confusion, attention-pattern issues, and agent performance degradation caused by accumulated or conflicting context.