Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/the-odds-api-automation
Automate The Odds API tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 19 of 22 test cases with the skill, and 6 of 22 without it.
and 17 more in the full report
15 fixed7 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
When discovering tools for historic odds retrieval, `RUBE_SEARCH_TOOLS` returned a tool payload that contains a `schemaRef` field instead of an inline JSON schema. Which specific Rube tool should be called to retrieve the complete input schema before invocation?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the user to call RUBE_GET_TOOL_SCHEMAS for tools returning schemaRef. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate The Odds API operations through Composio's The Odds API toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/the_odds_api
RUBE_MANAGE_CONNECTIONS with toolkit the_odds_apiRUBE_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 the_odds_apiAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "The Odds API 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 The Odds API task"}]
test cases passed, vs 6 / 22 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.