Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/modelry-automation
Automate Modelry tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 19 of 23 test cases with the skill, and 6 of 23 without it.
and 16 more in the full report
14 fixed7 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
During tool discovery, `RUBE_SEARCH_TOOLS` returned a Modelry tool that contains a `schemaRef` field instead of an inline JSON schema. Which Rube MCP action should be called to retrieve the full parameter schema?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies calling RUBE_GET_TOOL_SCHEMAS to fetch the full parameter schema. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Modelry operations through Composio's Modelry toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/modelry
RUBE_MANAGE_CONNECTIONS with toolkit modelryRUBE_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 modelryAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Modelry 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 Modelry task"}]
test cases passed, vs 6 / 23 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.