What is Veo Automation via Rube MCP?

It’s a workflow that automates Veo operations by discovering current tool schemas through RUBE_SEARCH_TOOLS and executing chosen tools via RUBE_MULTI_EXECUTE_TOOL within an active Veo connection.

Do I need API keys to use this skill?

No API keys are required. You just add the MCP server URL (https://rube.app/mcp) and ensure connectivity and active Veo Toolkit access.

What common mistakes should I avoid?

Don’t hardcode tool slugs or arguments; always fetch schemas with RUBE_SEARCH_TOOLS. Verify the Veo connection is ACTIVE before execution and include the memory parameter in multi-execute calls.

veo-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/veo-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Veo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/veo

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["veo"]
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 Veo-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `veo`
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/veo-automation/SKILL.mdView on GitHub

Overview

Veo Automation via Rube MCP orchestrates Veo operations using Composio's Veo toolkit. It relies on connected Rube MCP and an active Veo connection, and mandates always searching for current tool schemas before execution to avoid hardcoded slugs.

How This Skill Works

The workflow discovers available Veo tools with RUBE_SEARCH_TOOLS, then verifies the Veo connection via RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL. Tool schemas are fetched fresh each time to ensure compatibility, with memory and session handling essential for reliable runs.

When to Use It

You need to automate repetitive Veo operations using up-to-date tool schemas.
You're integrating Veo tasks into a larger Composio workflow and want consistent sessions.
You want to validate and use newly discovered tool schemas before execution.
You’re setting up or rechecking the Veo connection and toolkit status.
You need to batch or bulk execute multiple Veo tools within a single session.

Quick Start

Step 1: Get Rube MCP — add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify availability and connect — ensure RUBE_SEARCH_TOOLS responds and call RUBE_MANAGE_CONNECTIONS with toolkit 'veo' to activate Veo.
Step 3: Discover tools and execute — use RUBE_SEARCH_TOOLS to find a tool_slug, then run RUBE_MULTI_EXECUTE_TOOL with proper arguments, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Ensure RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from search results; avoid hardcoding slugs.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens when discovering tools.

Example Use Cases

Discover Veo tool slugs with RUBE_SEARCH_TOOLS, then execute a specific tool using RUBE_MULTI_EXECUTE_TOOL with proper arguments.
Establish a Veo connection via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before running workflows.
Run a sequence of Veo tools in a single session by reusing session_id and providing memory in each RUBE_MULTI_EXECUTE_TOOL call.
Review full tool schemas using RUBE_GET_TOOL_SCHEMAS to verify schemaRef and required fields before execution.
Handle pagination in RUBE_SEARCH_TOOLS responses to complete tool discovery for a complex Veo task.

Frequently Asked Questions

Add this skill to your agents