$ ~/registry/skill/composiohq-composio-skills-veo-automation

SKILL

veo-automation

Name: veo-automation
Author: Composio

Automate Veo workflows through Rube MCP with tool schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is primarily an instructional/prompt-style wrapper with no declared local secrets, file access, or direct code execution. However, it relies on remote Rube MCP and Veo connections, so actual operations and data flows pass through third-party services, making the overall posture low to moderate concern. The high-star open-source GitHub source materially lowers supply-chain risk, though license and maintenance status are not explicit in the provided materials.

CredentialsCaution

The material states the skill itself requires no local API key, but it requires establishing a Veo connection via `RUBE_MANAGE_CONNECTIONS` and completing external authentication, which implies third-party account tokens are involved in practice. No clear red flags of requesting unrelated credentials or prompting credential leakage are present.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and interacting with the Veo toolkit through Composio/Rube; user inputs, tool arguments, and session data may therefore be sent to those declared services. This is standard network behavior for a remote MCP, and there is no specific evidence of exfiltration to unknown or unrelated domains.

Code executionLow risk

The objective checks classify this as prompt-only, and the material is mainly workflow guidance and tool-calling order. It does not declare launching local processes, executing scripts, or requesting system-level execution privileges; `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH` point to remote tool orchestration rather than local code execution.

Data accessCaution

No direct local file read/write or host resource access is declared. However, when Veo operations are executed via remote tools, task arguments, session IDs, connection status, and possibly business data will be processed by third-party services. The provided material does not confirm data minimization or retention details.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (64.7k stars), providing good auditability and source credibility. The material shows no obfuscated install scripts, suspicious download commands, or obvious injection indicators. The missing license declaration and unknown maintenance status are worth noting, but not enough on their own to raise this to high risk.

Recommendations

Only connect accounts after reviewing and trusting the Rube/Composio and Veo terms and privacy posture, and keep scopes minimal.
Before production use, inspect the schemas returned by `RUBE_SEARCH_TOOLS` to avoid sending unnecessary sensitive fields.
Validate the workflow in an isolated project or test account first to confirm session data and outputs are not overshared.
Check the repository license, recent commits, and issue maintenance status before long-term adoption.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "veo-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/veo-automation/SKILL.md
2. Save it as ~/.claude/skills/veo-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Venly workflows via Rube MCP with schema lookup first.

ComposioGet→

$ loading_