Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/radar-automation
Automate Radar tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 13 of 18 test cases with the skill, and 5 of 18 without it.
and 10 more in the full report
11 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When searching for Radar tools via RUBE_SEARCH_TOOLS, what key should be used inside objects in the queries array to specify the task?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies using the use_case field inside objects in the queries array. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Radar operations through Composio's Radar toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/radar
RUBE_MANAGE_CONNECTIONS with toolkit radarRUBE_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 radarAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Radar 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 Radar task"}]
test cases passed, vs 5 / 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.