Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/moco-automation
Automate Moco tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 11 of 18 test cases with the skill, and 6 of 18 without it.
and 7 more in the full report
7 fixed7 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am constructing a call to execute a discovered Moco task tool using RUBE_MULTI_EXECUTE_TOOL. Do I need to include the memory parameter if I have no stored state from previous steps?
| Checked | Without skill | With skill |
|---|---|---|
| Confirms memory parameter must be present in RUBE_MULTI_EXECUTE_TOOL calls. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Moco operations through Composio's Moco toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/moco
RUBE_MANAGE_CONNECTIONS with toolkit mocoRUBE_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 mocoAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Moco 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 Moco task"}]
test cases passed, vs 6 / 18 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.