home / skills / composiohq / awesome-claude-skills / aero-workflow-automation

aero-workflow-automation skill

safe

/aero-workflow-automation

This skill automates Aero Workflow tasks through Rube MCP, always discovering current tool schemas before execution to ensure reliable, up-to-date automation.

npx playbooks add skill composiohq/awesome-claude-skills --skill aero-workflow-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: aero-workflow-automation
description: "Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `aero_workflow`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Aero Workflow tasks through Composio's Aero Workflow toolkit using Rube MCP. It provides a clear, repeatable pattern for discovering tools, validating connections, and executing multi-step workflow calls while handling pagination, sessions, and memory requirements. Always search tools first to retrieve current tool schemas before running any operations.

How this skill works

The skill uses RUBE_SEARCH_TOOLS to discover available Aero Workflow tool slugs and input schemas, then validates an active connection via RUBE_MANAGE_CONNECTIONS for the aero_workflow toolkit. After confirming the connection and session, it executes actions using RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk operations) with schema-compliant arguments and an explicit memory object. It also supports fetching full schemas via RUBE_GET_TOOL_SCHEMAS and handling paginated responses.

When to use it

When you need to orchestrate Aero Workflow actions programmatically through Composio.
Before executing any workflow step to ensure tool schemas and slugs are up to date.
When running multi-step or bulk operations that require coordinated session and memory handling.
When automating recurring Aero Workflow tasks across environments or users.
When you need to fetch full tool schemas or run composio tools via a remote workbench.

Best practices

Always call RUBE_SEARCH_TOOLS first; do not hardcode tool slugs or argument shapes.
Confirm RUBE_MANAGE_CONNECTIONS shows ACTIVE for the aero_workflow toolkit before executing tools.
Include an explicit memory object (even empty) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs for a single workflow and generate new session IDs for separate workflows.
Respect exact field names and types from the returned schemas and handle pagination tokens.

Example use cases

Discover available Aero Workflow operations and run a single schema-compliant task via RUBE_MULTI_EXECUTE_TOOL.
Run a batch process across multiple Aero Workflow tools using RUBE_REMOTE_WORKBENCH and run_composio_tool().
Automate a multi-step approval workflow by reusing a session_id and passing state through memory.
Fetch full tool definitions with RUBE_GET_TOOL_SCHEMAS to build a UI or validate inputs before execution.

FAQ

What is the first API call I must make?

Always call RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas for your Aero Workflow use case.

What if my RUBE_MANAGE_CONNECTIONS status is not ACTIVE?

Follow the returned auth link to complete setup, then re-check RUBE_MANAGE_CONNECTIONS until the toolkit shows ACTIVE.