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

SKILL

autobound-automation

Name: autobound-automation
Author: Composio

Automate Autobound 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.7k

Summary

This appears to be a prompt/documentation-style open-source skill that does not itself require local secrets or describe direct local code execution or file access. The main security consideration is its guidance to connect to third-party Rube MCP and Autobound services, which introduces normal external service interaction and account authorization surface, but no clear red flags warranting a high-risk rating were found.

CredentialsCaution

The material lists no local keys or environment variables, but the README explicitly requires establishing an `autobound` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link when the connection is not active. This means the skill itself does not hold secrets, but it does guide users to grant account connection permissions to third-party services, which is a normal credential/authorization surface and should be reviewed for scope and destination.

Network egressCaution

The README instructs users to configure `https://rube.app/mcp` as an MCP server and use Composio/Rube to discover and execute Autobound tools. This implies that requests, session IDs, tool arguments, and potentially business data may be sent through that remote service path. No unrelated endpoints are declared, and this is consistent with the stated functionality, so it is rated as caution rather than high risk.

Code executionLow risk

Based on the objective checks, this is a `prompt-only` skill. The material is primarily workflow guidance and does not describe spawning local processes, running scripts, or requesting system-level execution permissions. Although it mentions `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, that is remote tool orchestration guidance and does not by itself show local code execution by the skill.

Data accessLow risk

The material does not declare reading or writing local files, databases, clipboard, or other host resources, nor does it request additional local permissions. The accessible data scope appears mainly limited to business objects available after the remote Autobound account connection, with no described local data access beyond the stated purpose.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (about 64.7k stars), both of which are meaningful risk-reducing signals. This entry also appears to be a reviewable skill description rather than a closed-source binary. The missing license declaration and unknown maintenance status are minor information gaps, but not enough to raise it to high risk in the absence of other red flags.

Recommendations

Before connecting to `rube.app/mcp`, review its privacy policy, data retention practices, and whether it logs tool arguments or session content.
When authorizing `autobound`, prefer least-privilege accounts and periodically review or revoke connections that are no longer needed.
Before production use, validate the actual data egress scope of `RUBE_SEARCH_TOOLS` and execution flows with low-sensitivity test data.
Pin and review the specific GitHub repository version/commit you rely on, and monitor ongoing maintenance and change history.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Autobound Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/autobound

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["autobound"]
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 Autobound-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `autobound`
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 AI/ML API workflows via Rube MCP, checking latest tool schemas first.

ComposioGet→

$ loading_