slackbot-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/slackbot-automation --openclawSlackbot Automation via Rube MCP
Automate Slackbot operations through Composio's Slackbot toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/slackbot
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Slackbot connection via
RUBE_MANAGE_CONNECTIONSwith toolkitslackbot - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitslackbot - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Slackbot operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Slackbot task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["slackbot"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Slackbot-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit slackbot |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/slackbot-automation/SKILL.mdView on GitHub Overview
Slackbot Automation via Rube MCP lets you orchestrate Slackbot operations through Composio's toolkit by discovering current tool schemas, verifying an active Slackbot connection, and executing tools without hardcoding slugs. This makes Slackbot workflows resilient to schema updates and simplifies complex automation sequences.
How This Skill Works
Technically, you first call RUBE_SEARCH_TOOLS to fetch available Slackbot tools and their input schemas. Then you verify the Slackbot connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, you run a tool using RUBE_MULTI_EXECUTE_TOOL, passing the discovered slug, a memory payload, and the session_id, allowing multi-step workflows and pagination as needed.
When to Use It
- When you need to automate Slackbot operations by discovering tools at runtime.
- When setting up a new Slackbot workflow that requires establishing an active connection before execution.
- When you must always fetch current tool schemas to avoid hardcoding slugs.
- When orchestrating a multi-step Slackbot task that involves discovering, connecting, and executing tools in sequence.
- When tools return paginated results and you need to fetch additional pages to complete the task.
Quick Start
- Step 1: Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds and returns tool schemas.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit slackbot and ensure the status is ACTIVE.
- Step 3: Discover a Slackbot tool with RUBE_SEARCH_TOOLS for your task, then execute it using RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any tool to get current slugs and schemas.
- Check RUBE_MANAGE_CONNECTIONS status and ensure ACTIVE prior to execution.
- Use exact field names and types from the search results to avoid schema mismatch.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow; generate new sessions for new workflows and handle pagination tokens.
Example Use Cases
- Discover Slackbot tools with RUBE_SEARCH_TOOLS for Slackbot operations and post a message using a discovered tool slug.
- Connect Slackbot with RUBE_MANAGE_CONNECTIONS and then fetch available channels using the corresponding tool.
- Build a small workflow to send scheduled messages by using a discovered tool and referencing a session_id.
- Iterate over multiple channels by repeatedly executing a tool slug discovered earlier, handling memory between calls.
- Run a sequence of Slackbot actions in a single session, reusing the session_id and ensuring the tool schemas are current before each step.