Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/visme-automation
Automate Visme tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 18 of 21 test cases with the skill, and 10 of 21 without it.
and 8 more in the full report
9 fixed10 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
During tool discovery via Rube MCP for Visme, one of the returned tool objects contains a `schemaRef` field rather than an inline full schema. Which tool should be called to fetch the complete input schema for that tool?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies RUBE_GET_TOOL_SCHEMAS as the function to call | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Visme operations through Composio's Visme toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/visme
RUBE_MANAGE_CONNECTIONS with toolkit vismeRUBE_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 vismeAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Visme 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 Visme task"}]
test cases passed, vs 10 / 21 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.