Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/respond-io-automation
Automate Respond IO tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 20 of 24 test cases with the skill, and 7 of 24 without it.
and 14 more in the full report
13 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
If an older script uses 'contact_email' as argument key but the newly searched tool schema specifies 'email', which key must be provided in RUBE_MULTI_EXECUTE_TOOL?
| Checked | Without skill | With skill |
|---|---|---|
| Requires using exact argument field names returned by RUBE_SEARCH_TOOLS | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Respond IO operations through Composio's Respond IO toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/respond_io
RUBE_MANAGE_CONNECTIONS with toolkit respond_ioRUBE_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 respond_ioAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Respond IO 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 Respond IO task"}]
test cases passed, vs 7 / 24 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.