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

SKILL

aero-workflow-automation

Name: aero-workflow-automation
Author: Composio

Automate Aero Workflow tasks via Rube MCP using current tool schemas.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself is an open-source prompt/document artifact with no direct local secret requirement and no embedded executable code. However, it is designed to connect to remote Rube MCP/Composio services and invoke external tools, so normal remote connectivity and potential data egress should be treated with caution overall.

CredentialsCaution

The material claims 'no API keys needed,' but prerequisites require an ACTIVE `aero_workflow` connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link, implying third-party OAuth/account authorization in practice. No local environment variables are requested here, but users should review external account scopes and token binding risks.

Network egressCaution

The README explicitly instructs adding the remote MCP server `https://rube.app/mcp` and links to `composio.dev` documentation. Using `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL` will likely send task parameters, session IDs, connection state, and workflow-related data to those declared external services. This is normal egress for a remote tool, with no undisclosed or unrelated endpoints evident in the material.

Code executionLow risk

The system marks this skill as `prompt-only`; the provided content is limited to usage guidance and invocation patterns, with no install script, shell commands, local process launch steps, or requests for elevated system permissions. Any tool execution described occurs within the external MCP/Composio ecosystem, not as direct local code execution by this skill itself.

Data accessCaution

The skill itself does not declare direct local file or system access, but it does guide users to send workflow requests, `memory` content, and session information to remote tools and to connect external Aero Workflow resources. The effective data-access scope depends on the Rube/Composio tool schemas and the permissions of the connected account, and the material does not provide granular least-privilege details.

Supply chainLow risk

The source is an open GitHub repository, and the system flags it as `open-source` with strong community adoption (64.7k stars), which are meaningful risk-reducing signals. No closed-source binary, obfuscated installer, or suspicious dependency list is shown here; although the license is unspecified and maintenance status is unknown, the supply-chain risk remains relatively low given its prompt-only nature and strong community trust.

Recommendations

Only connect this MCP if you trust `rube.app` and Composio, and verify the actual auth page domain and requested scopes.
Apply least privilege when linking the Aero Workflow account; avoid granting write or org-wide access unrelated to the task.
Do not send unnecessary sensitive content to `RUBE_*` tools, especially in session notes, memory fields, or business-confidential inputs.
Test in an isolated environment first and document what data the external tools can see and what actions they perform.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Aero Workflow Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/aero_workflow

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["aero_workflow"]
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 Aero Workflow-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `aero_workflow`
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_