aero-workflow-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/aero-workflow-automation --openclawAero 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_CONNECTIONSwith toolkitaero_workflow - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitaero_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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/aero-workflow-automation/SKILL.mdView on GitHub Overview
This skill automates Aero Workflow tasks using Composio's Aero Workflow toolkit through Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and ensuring an ACTIVE connection via RUBE_MANAGE_CONNECTIONS. Following the core pattern reduces errors from schema drift and connection mishaps.
How This Skill Works
Begin by discovering available Aero tools with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas. Then verify and establish an ACTIVE connection using RUBE_MANAGE_CONNECTIONS for the aero_workflow toolkit. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing exact schema-compliant arguments, a memory object, and an active session.
When to Use It
- When you need to automate an Aero Workflow task with the latest tool schemas (must call RUBE_SEARCH_TOOLS first).
- When setting up or validating a new Aero Workflow connection and toolkit with RUBE_MANAGE_CONNECTIONS.
- When selecting a tool for execution based on current discovery results from RUBE_SEARCH_TOOLS.
- When performing multi-tool execution using RUBE_MULTI_EXECUTE_TOOL in a single session.
- When reusing sessions across a workflow and handling pagination in tool results.
Quick Start
- Step 1: Discover tools with RUBE_SEARCH_TOOLS using your Aero Workflow use_case.
- Step 2: Establish and verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the aero_workflow toolkit.
- Step 3: Execute a selected tool with RUBE_MULTI_EXECUTE_TOOL, passing schema-compliant arguments, memory, and a session.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
- Ensure the connection status is ACTIVE before executing tools with RUBE_MANAGE_CONNECTIONS.
- Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
- Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and handle pagination tokens when results span pages.
Example Use Cases
- Automate a daily Aero data ingestion by discovering tools, establishing an ACTIVE connection, and executing a single tool with an empty memory.
- Run a batch of Aero tasks by discovering tools once, then executing multiple tools in a single session using RUBE_MULTI_EXECUTE_TOOL.
- Validate and refresh the aero_workflow connection at the start of a long-running workflow to prevent drift.
- Handle pagination when RUBE_SEARCH_TOOLS returns multiple pages of tool results and continue fetching until complete.
- Avoid hardcoding tool slugs; rely on RUBE_SEARCH_TOOLS output for dynamic, current tool schemas.
