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

SKILL

v0-automation

Name: v0-automation
Author: Composio

Automate V0 workflows via Rube MCP using current tool schemas 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 essentially an open-source prompt template with strong public provenance and no obvious high-risk red flags. The main concern is that its real functionality depends on external Rube MCP and V0/Composio connections, which may send task inputs and related data to third-party services during use.

CredentialsCaution

The material says the skill itself needs no API key, but the README explicitly requires establishing a `v0` connection via `RUBE_MANAGE_CONNECTIONS` and completing authorization through a returned auth link if inactive. Credentials therefore live mainly in the external Rube/V0 integration path; the skill does not directly request secrets, but third-party connection grants still create account-abuse exposure.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and performing actions through Composio/V0 tooling. This means user queries, tool arguments, session IDs, and possibly business data may be sent to Rube/Composio/V0-related services. The endpoint is explicitly documented rather than unknown, but it should still be treated as third-party egress.

Code executionLow risk

Based on the provided material, this is a prompt-only skill that mainly describes workflows for calling `RUBE_SEARCH_TOOLS`, `RUBE_MANAGE_CONNECTIONS`, and `RUBE_MULTI_EXECUTE_TOOL`. It does not describe directly spawning local processes, running scripts, or requesting extra system privileges. Any execution capability depends on external MCP tools rather than local code execution by the skill itself.

Data accessCaution

The material does not show the skill directly reading or writing local files, but it does guide external tools to access data and operational resources under the V0 connection, and it requires session reuse, passing `memory`, and submitting schema-based arguments. The effective data-access scope depends on the permissions of the connected V0/Composio tools, so their actual visibility should be reviewed before use.

Supply chainCaution

Positive signals include being open source, hosted on GitHub, having very strong community adoption (64.7k stars), and appearing to be mostly auditable README/prompt content. Points to watch are the unspecified license, unknown maintenance status, and the fact that real functionality depends on off-repo Rube MCP and Composio/V0 services plus dynamic schemas, so the supply-chain boundary is not limited to this repository alone.

Recommendations

Before connecting to `https://rube.app/mcp`, verify its privacy policy, data retention practices, and operating entity, and enable it only when needed.
Use least-privilege authorization when linking a V0 account, and avoid granting access unrelated to the current automation task.
Before production use, review the exact tool schemas and executable actions returned by `RUBE_SEARCH_TOOLS` to ensure they do not touch sensitive projects or data.
Test the skill and its external MCP dependencies in an isolated environment first, and log outbound requests and authorization changes.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

V0 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/v0

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["v0"]
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 V0-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `v0`
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 Veo workflows through Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_