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

SKILL

botpress-automation

Name: botpress-automation
Author: Composio

Automate Botpress tasks and workflow actions through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily a prompt-style workflow description and does not itself declare local execution, file access, or direct secret requirements. However, it relies on remote Rube MCP and external Botpress/Composio connections for tool discovery and execution, which introduces normal caution around external services and authorization; the high-star open-source source materially lowers overall risk.

CredentialsCaution

The material says no API key is needed to add Rube MCP, but it also requires creating an ACTIVE Botpress connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth-link flow, which implies third-party account authorization tokens may be involved. No local system-level secret request or explicit credential-abuse red flag is shown.

Network egressCaution

It explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using the Composio/Botpress toolchain for search, connection, and execution. This means task context and tool arguments may be sent to the stated external services. The endpoint appears relevant and declared; there is no evidence of exfiltration to unknown or unrelated domains.

Code executionLow risk

Based on the provided material, this is a prompt/README-style skill describing remote tool calls such as `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL`. It does not declare spawning local processes, running scripts, or requesting additional system permissions.

Data accessCaution

The material does not declare direct access to local files or local databases. However, when executing automation through remote Botpress tools, it may access data and resources within the user's authorized Botpress account/workspace. No overbroad local data access beyond the stated purpose is described.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (~64.9k stars), providing good auditability and credibility. While the license and maintenance status are not clearly stated, the current material shows no closed-source delivery, suspicious install script, or obvious supply-chain red flag.

Recommendations

Only add `https://rube.app/mcp` in a trusted client, and verify your organization permits sending task data to Rube/Composio/Botpress.
Use least-privilege authorization when connecting the Botpress account, and periodically review/revoke unused connections or sessions.
Before production use, validate with non-sensitive test data which resources `RUBE_MULTI_EXECUTE_TOOL` can actually reach.
Review the relevant open-source repository and tool documentation for maintenance status, privacy terms, and concrete data flows.

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 "botpress-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/botpress-automation/SKILL.md
2. Save it as ~/.claude/skills/botpress-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Botpress Automation via Rube MCP

Automate Botpress operations through Composio's Botpress toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/botpress

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Botpress connection via RUBE_MANAGE_CONNECTIONS with toolkit botpress
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 botpress
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: "Botpress 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 Botpress task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["botpress"]
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 Botpress-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `botpress`
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 Autom workflows via Rube MCP while checking current tool schemas first.

ComposioGet→

$ loading_