Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/veriphone-automation
Automate Veriphone 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 7 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.
Which toolkit string should be supplied to RUBE_MANAGE_CONNECTIONS when checking if phone verification tool access is enabled?
| Checked | Without skill | With skill |
|---|---|---|
| Passes 'veriphone' in the toolkits parameter. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Veriphone operations through Composio's Veriphone toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/veriphone
RUBE_MANAGE_CONNECTIONS with toolkit veriphoneRUBE_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 veriphoneAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Veriphone 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 Veriphone 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.