Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/minerstat-automation
Automate Minerstat tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 4 of 16 test cases with the skill, and 4 of 16 without it.
2 fixed3 passed either way15 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to look up tools for checking diagnostic alerts on my mining farm via Rube MCP. How should the query parameter be structured?
| Checked | Without skill | With skill |
|---|---|---|
| Passes query object with use_case field to RUBE_SEARCH_TOOLS | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Minerstat operations through Composio's Minerstat toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/minerstat
RUBE_MANAGE_CONNECTIONS with toolkit minerstatRUBE_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 minerstatAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Minerstat 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 Minerstat task"}]
test cases passed, vs 4 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.