Install any skill in seconds. Free to start, no credit card required.
Get Started Free →openteams-lab/woodpecker-co-automation
Automate Woodpecker co tasks via Rube MCP (Composio). Always search tools first for current schemas.
Passed 12 of 18 test cases with the skill, and 5 of 18 without it.
and 13 more in the full report
10 fixed5 passed either way6 still failing1 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.
In a Woodpecker co workflow using Rube MCP, if tool search has been completed, what step must happen before calling execution tools like `RUBE_MULTI_EXECUTE_TOOL`?
| Checked | Without skill | With skill |
|---|---|---|
| Checks connection status via RUBE_MANAGE_CONNECTIONS before executing tools | Missed | Passed |
| Ensures the connection status is ACTIVE before running execution calls | Missed | Passed |
The instructions your model reads when the skill loads.
Automate Woodpecker co operations through Composio's Woodpecker co toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/woodpecker_co
RUBE_MANAGE_CONNECTIONS with toolkit woodpecker_coRUBE_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 woodpecker_coAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Woodpecker co 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 Woodpecker co 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.