aivoov-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/aivoov-automation --openclawAivoov Automation via Rube MCP
Automate Aivoov operations through Composio's Aivoov toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/aivoov
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Aivoov connection via
RUBE_MANAGE_CONNECTIONSwith toolkitaivoov - 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 toolkitaivoov - 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: "Aivoov 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 Aivoov task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["aivoov"]
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 Aivoov-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit aivoov |
| 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/aivoov-automation/SKILL.mdView on GitHub Overview
Automate Aivoov operations through Composio's Aivoov toolkit via Rube MCP. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an active Aivoov connection. Always query tool schemas before running workflows.
How This Skill Works
Discover available Aivoov tools with RUBE_SEARCH_TOOLS to obtain input schemas and execution plans. Then verify the Aivoov connection with RUBE_MANAGE_CONNECTIONS and execute chosen tools with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and schema-compliant arguments, including a memory object and session_id.
When to Use It
- Automating routine Aivoov operations and task sequences
- When tool schemas change and you need current slugs/arguments
- During integration sprints to ensure reproducible workflows
- For bulk Aivoov actions using RUBE_REMOTE_WORKBENCH
- When reusing a workflow session across multiple steps
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Verify RUBE_SEARCH_TOOLS responds and fetch Aivoov tool schemas
- Step 3: Discover tools, check ACTIVE connection with RUBE_MANAGE_CONNECTIONS, and execute tools with RUBE_MULTI_EXECUTE_TOOL
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Ensure the Aivoov connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution
- Use exact field names and types from the tool schemas (no hardcoding)
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
- Reuse session IDs within a workflow and generate new ones for new workflows
Example Use Cases
- Automate a daily Aivoov operation by discovering tools, connecting to Aivoov, and issuing a tool with a session_id.
- Update an existing workflow after a schema change by re-running RUBE_SEARCH_TOOLS to fetch new slugs and arguments.
- Run multiple Aivoov tasks in sequence by reusing a single session_id across RUBE_MULTI_EXECUTE_TOOL calls.
- Perform bulk Aivoov actions using RUBE_REMOTE_WORKBENCH and run_composio_tool().
- Inspect all available tool schemas with RUBE_GET_TOOL_SCHEMAS to plan integration.
