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

SKILL

autom-automation

Name: autom-automation
Author: Composio

Automate Autom workflows via Rube MCP while checking current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially an open-source prompt/workflow wrapper with no declared local secrets, file access, or direct system execution. The main exposure comes from connecting the client to Rube MCP and using it to manage an external Autom integration, so the overall posture is low-to-moderate risk with mostly caution-level concerns.

CredentialsCaution

The material says the skill itself requires no environment variables or API keys, but actual use requires creating and activating an `autom` connection via `RUBE_MANAGE_CONNECTIONS`, implying credentials are likely held by Rube/Composio or obtained through an external auth flow. No explicit credential-abuse red flags are shown, but third-party account authorization is involved, so token scope and storage should be reviewed.

Network egressCaution

The README explicitly instructs users to add `https://rube.app/mcp` as an MCP server and use Rube/Composio for tool discovery, connection management, and remote operations. This means task inputs, session IDs, tool arguments, and possibly business data may be transmitted to external services. The endpoint is explicitly named rather than unknown, but this is still a standard external data-egress scenario.

Code executionLow risk

Based on the material, this is a prompt-only workflow wrapper and does not describe starting local processes, executing shell commands, installing binaries, or requesting system-level execution privileges. Its actions are primarily calls to existing MCP tools and remote services, so no local code-execution red flags are evident.

Data accessCaution

There is no stated direct access to the local filesystem, clipboard, or device resources, but once the Autom connection is active, the Rube tools can query or act on data within the authorized Autom account/workflows. The effective data-access scope depends on the permissions granted to that external connection, which is a standard third-party integration concern.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (about 64.7k stars). It is also marked as open-source and prompt-only, both of which materially lower risk. Although the license is unspecified and maintenance status is unknown, the current material shows no closed-source, unknown-origin, or obvious injection-style red flags, so overall supply-chain risk appears low.

Recommendations

Before adding `https://rube.app/mcp`, confirm your organization permits sending task content and tool parameters to Rube/Composio, and review their privacy and retention policies.
Use least-privilege authorization for the Autom connection, limiting access to only the accounts and actions required for the task.
Validate the actual behavior of `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and execution tools with non-sensitive test data before production use.
Where possible, restrict the allowed MCP server and tool scope, and retain session IDs, execution parameters, and audit logs.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Autom Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/autom

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["autom"]
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 Autom-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `autom`
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 Kit tasks via Rube MCP with schema lookup first.

ComposioGet→

$ loading_