What is the first step before executing any Vero tool?

Always call RUBE_SEARCH_TOOLS to obtain current tool schemas and avoid hardcoding slugs or arguments.

How do I ensure my connection to Vero is ready for execution?

Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE for the vero toolkit before running any tools.

vero-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Vero Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/vero

Prerequisites

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

Step 2: Check Connection

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

Overview

Vero Automation via Rube MCP enables automating Vero operations using Composio's Vero toolkit. It emphasizes discovering current tool schemas before running anything to prevent drift and ensure compatibility.

How This Skill Works

Connect to Rube MCP and verify the environment, then discover available Vero tools with RUBE_SEARCH_TOOLS. After selecting a tool, manage the Vero connection with RUBE_MANAGE_CONNECTIONS and execute the tool via RUBE_MULTI_EXECUTE_TOOL, always including memory and a valid session_id. This workflow relies on up-to-date schemas, so avoid hardcoding slugs or arguments.

When to Use It

You need to automate a Vero workflow by leveraging Composio's Vero toolkit through Rube MCP.
You must fetch current tool schemas before running any Vero-related tasks.
You need to establish or verify an ACTIVE Vero connection before execution.
You want to execute a discovered Vero tool using RUBE_MULTI_EXECUTE_TOOL with proper memory and session handling.
You want to adapt workflows as tool schemas change and avoid hardcoding slugs or parameters.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as your MCP server and ensure RUBE_SEARCH_TOOLS responds.
Step 2: Use RUBE_SEARCH_TOOLS for your Vero task to discover available tools and their schemas, noting slugs and required fields.
Step 3: Run RUBE_MANAGE_CONNECTIONS for the vero toolkit, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, memory, and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to retrieve current Vero tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Automate a daily Vero status report by discovering the appropriate tool and executing it with an active session.
Set up a Vero update flow by discovering tools, validating the connection, and running the selected tool with memory and session_id.
Fetch the latest Vero tool schemas and run a parameterized task without hardcoding the slug.
Reuse a session across a batch of Vero tasks to maintain context within a single automation.
Handle pagination when listing tools with RUBE_SEARCH_TOOLS and execute multiple tools in sequence.

Frequently Asked Questions

Add this skill to your agents