Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/piloterr-automation
Automate Piloterr tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 12 of 17 test cases with the skill, and 6 of 17 without it.
and 11 more in the full report
10 fixed6 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
During tool search for Piloterr operations, one returned tool has a `schemaRef` field instead of an inline schema. Which Rube MCP tool must be called to fetch the full JSON schema before constructing input arguments?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies calling RUBE_GET_TOOL_SCHEMAS to obtain the schema. | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Piloterr operations through Composio's Piloterr toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/piloterr
RUBE_MANAGE_CONNECTIONS with toolkit piloterrRUBE_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 piloterrAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Piloterr 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 Piloterr task"}]
test cases passed, vs 6 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.