Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/qualaroo-automation
Automate Qualaroo tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 5 of 15 test cases with the skill, and 3 of 15 without it.
3 fixed4 passed either way15 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am starting a brand new workflow to manage Qualaroo nudges. How should tool discovery be initialized with session tracking?
| Checked | Without skill | With skill |
|---|---|---|
| The response sets generate_id to true inside the session object during RUBE_SEARCH_TOOLS execution. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Qualaroo operations through Composio's Qualaroo toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/qualaroo
RUBE_MANAGE_CONNECTIONS with toolkit qualarooRUBE_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 qualarooAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Qualaroo 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 Qualaroo task"}]
test cases passed, vs 3 / 15 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.