Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/vero-automation
Automate Vero tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 16 of 20 test cases with the skill, and 7 of 20 without it.
and 13 more in the full report
10 fixed8 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
What MCP endpoint URL should be configured in our AI client settings to access the Rube tools for Vero, and what API key should be attached in the request headers?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies https://rube.app/mcp as the server endpoint URL. | Missed | Passed |
| The response states that no API key is required in the request headers. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Vero operations through Composio's Vero toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/vero
RUBE_MANAGE_CONNECTIONS with toolkit veroRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit veroAlways 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.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Vero task"}]
test cases passed, vs 7 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.