playbooks

home / skills / composiohq / awesome-claude-skills / aivoov-automation

aivoov-automation skill

/aivoov-automation

This skill automates Aivoov operations via Rube MCP toolkits, discovering current schemas before execution to ensure accurate tool usage.

npx playbooks add skill composiohq/awesome-claude-skills --skill aivoov-automation

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

Files (1)
SKILL.md
2.8 KB
---
name: aivoov-automation
description: "Automate Aivoov tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Aivoov Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/aivoov](https://composio.dev/toolkits/aivoov)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Aivoov connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `aivoov`
- 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 `aivoov`
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: "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_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 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](https://composio.dev)*

Overview

This skill automates Aivoov operations through Composio’s Aivoov toolkit using the Rube MCP interface. It provides a safe, repeatable pattern for discovering tools, validating connections, and executing multi-step workflows with schema-aware calls. The skill emphasizes always searching for current tool schemas before running actions.

How this skill works

The skill first calls RUBE_SEARCH_TOOLS to discover available Aivoov tool slugs, input schemas, and recommended execution plans. It then verifies or establishes an Aivoov connection via RUBE_MANAGE_CONNECTIONS and confirms ACTIVE status. Finally it executes one or more tools using RUBE_MULTI_EXECUTE_TOOL (including a memory object and session id) or runs bulk jobs with RUBE_REMOTE_WORKBENCH.

When to use it

  • Automating repeatable Aivoov tasks or pipelines that require multiple toolkit calls.
  • Orchestrating workflows that depend on up-to-date tool schemas or changing tool sets.
  • Running bulk operations or remote workbench jobs against Aivoov via Composio.
  • Building integrations where session state and memory must be preserved across steps.

Best practices

  • Always call RUBE_SEARCH_TOOLS first — do not hardcode tool slugs or argument shapes.
  • Verify connection status with RUBE_MANAGE_CONNECTIONS and follow auth links when needed.
  • Include a memory parameter (even {}) in RUBE_MULTI_EXECUTE_TOOL calls.
  • Reuse session IDs within a workflow; create new sessions for new workflows.
  • Check for pagination tokens and fetch subsequent pages when tool responses are paginated.

Example use cases

  • Discovering the current Aivoov upload tool and executing a file ingestion workflow with validated schema fields.
  • Orchestrating a multi-step content processing pipeline that calls several Aivoov tools in sequence using RUBE_MULTI_EXECUTE_TOOL.
  • Running bulk transformations across many records using RUBE_REMOTE_WORKBENCH and run_composio_tool().
  • Automated checks that confirm the Aivoov connection is ACTIVE before nightly batch jobs run.

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; the endpoint works without API keys.

What if a tool schema changes?

Always re-run RUBE_SEARCH_TOOLS before execution to get the current schema. Update arguments to match exact field names and types returned by the search.