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

SKILL

composio-automation

Name: composio-automation
Author: Composio

Automate Composio tasks via Rube MCP with tool schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself appears to be an open-source prompt-style wrapper with no declared local secrets, file permissions, or direct code execution. However, it is designed around remote Rube MCP and Composio-connected tool execution, so it carries normal third-party authorization and network-use considerations, resulting in an overall low-to-moderate, mostly caution-level profile.

CredentialsCaution

The material says 'No API keys needed,' but actual use requires creating and activating a composio connection via RUBE_MANAGE_CONNECTIONS, which suggests credentials/authorization are likely managed by Rube/Composio rather than absent. Users should still review third-party connection scopes and token handling.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and using it for tool discovery, connection management, and tool execution. This means task arguments, session data, and possibly business data may pass through the stated third-party service, but there is no specific red flag indicating exfiltration to unknown or unrelated endpoints.

Code executionLow risk

System checks mark this as prompt-only, and the provided content is mainly workflow guidance and call ordering. It does not declare local process spawning, script execution, or system-level execution permissions; the execution described occurs in the external MCP/tool ecosystem rather than in the skill itself.

Data accessCaution

The skill itself does not declare direct local file read/write or access to local resources, but through RUBE_SEARCH_TOOLS, RUBE_MULTI_EXECUTE_TOOL, and Composio connections, it can indirectly operate on externally authorized resources. The real data access scope depends on the connections and tool permissions granted in Composio/Rube, so least-privilege setup is advisable.

Supply chainLow risk

The source is a GitHub open-source repository with very strong community adoption (64.7k stars), which materially lowers supply-chain risk. Although the license is unspecified and maintenance status is unknown, and the repo appears to be a skills collection rather than a standalone implementation, the available material shows no closed-source opacity, impersonation, or obvious injection-style red flags.

Recommendations

Grant only the minimum connection scopes needed for the current task in Rube/Composio, and review authorized apps regularly.
Avoid placing unnecessary sensitive data, customer data, or credentials into tool-call inputs before sending them.
Verify the privacy policy, data retention, and logging practices for rube.app/mcp and related Composio connections.
Check recent repository maintenance status and review how this skill is actually implemented in your client before use.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Composio Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/composio

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["composio"]
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 Composio-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `composio`
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 curated workflows with Rube MCP after checking current tool schemas first.

ComposioGet→

$ loading_