$ ~/registry/skill/composiohq-composio-skills-slackbot-automation

SKILL

slackbot-automation

Name: slackbot-automation
Author: Composio

Automate Slackbot messages, reminders, and teamwork workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt-only wrapper that instructs the model to use Composio's Slackbot toolkit through Rube MCP, with no visible local code execution or explicit API key requirement. The main security consideration is its reliance on a remote MCP service and subsequent Slack authorization flow, which is a normal external-integration risk rather than a clear high-risk red flag.

CredentialsCaution

The material says there are 'no API keys', but it still requires establishing a `slackbot` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link when the connection is not ACTIVE. This implies Slack or third-party OAuth/session authorization is still involved; no explicit leakage or abuse is described, but it should be treated as a normal credential-integration caution.

Network egressCaution

The README explicitly instructs adding the remote MCP server `https://rube.app/mcp` and using it to discover tools, manage connections, and execute Slackbot workflows; it also references `composio.dev` documentation. User instructions and arguments are therefore likely sent through Rube/Composio to external services, but the material does not show unknown or unrelated endpoints, nor any abnormal exfiltration red flags.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no executable install script, no requirement to spawn local processes, and no stated access to shell or privileged system capabilities. Its main behavior is to guide calls to external MCP tools rather than perform local code execution.

Data accessCaution

The skill's purpose is to 'Automate Slackbot operations,' so its data-access surface is mainly Slackbot/Slack-related resources after authorization. However, the README does not clearly bound what data can be read or written and instead emphasizes searching current tool schemas before execution. Its actual access scope therefore depends on downstream authorization and specific tool definitions, making this a normal but review-worthy external data access case.

Supply chainLow risk

The source is an open GitHub repository, and the objective checks mark it as `prompt-only` and `open-source`, with strong community adoption (64.7k stars), all of which are positive risk-reducing signals. Although the license is unspecified and maintenance status is unknown, and actual execution depends on external Rube/Composio services, the skill document itself is relatively low risk from a source and auditability perspective.

Recommendations

Only connect `https://rube.app/mcp` in a trusted environment, and verify your organization permits Slack-related requests to be routed through that service.
Before completing the `slackbot` authorization flow, review the exact OAuth/connection scopes requested and apply least privilege.
Inspect the actual tool schemas returned by `RUBE_SEARCH_TOOLS` before use to confirm they do not exceed the expected Slack data access.
For production use, validate behavior and data flows first in an isolated workspace or with a low-privilege account.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "slackbot-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/slackbot-automation/SKILL.md
2. Save it as ~/.claude/skills/slackbot-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Slackbot 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_CONNECTIONS with toolkit slackbot
Always call RUBE_SEARCH_TOOLS first 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_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit slackbot
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_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, 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

Automate Botpress tasks and workflow actions through Rube MCP.

ComposioGet→

$ loading_