Do I need API keys to use Rube MCP for Woodpecker co automation?

No. Add the MCP server at https://rube.app/mcp; no API keys are required to connect and fetch tool schemas.

How do I ensure I’m using current tool schemas?

Always call RUBE_SEARCH_TOOLS before executing any tool to obtain the latest slugs and input schemas; never hardcode tool slugs or arguments.

What if my Woodpecker co connection shows not ACTIVE?

Use RUBE_MANAGE_CONNECTIONS to check status; if not ACTIVE, follow the returned auth link to complete setup and then recheck until ACTIVE before running workflows.

woodpecker-co-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/woodpecker-co-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Woodpecker co Automation via Rube MCP

Automate Woodpecker co operations through Composio's Woodpecker co toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/woodpecker_co

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Woodpecker co connection via RUBE_MANAGE_CONNECTIONS with toolkit woodpecker_co
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit woodpecker_co
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always 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.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Woodpecker co task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["woodpecker_co"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Woodpecker co-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `woodpecker_co`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/woodpecker-co-automation/SKILL.md

View on GitHub

Overview

This skill automates Woodpecker co operations by leveraging Composio's Woodpecker co toolkit through Rube MCP. It emphasizes discovering current tool schemas first to avoid outdated tool slugs and schema mismatches, and requires an active MCP connection.

How This Skill Works

Connect to Rube MCP by adding the MCP endpoint and verify RUBE_SEARCH_TOOLS. Next, discover available Woodpecker co tools and their input schemas, ensure the connection via RUBE_MANAGE_CONNECTIONS is ACTIVE, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory payload.

When to Use It

When you need to automate Woodpecker co tasks without hardcoding tool slugs or schemas
When tool schemas update and you must fetch fresh slugs and arguments via RUBE_SEARCH_TOOLS
When setting up a new Woodpecker co workflow and you want validated connections
When performing a sequence of Woodpecker co tools in a single workflow with session continuity
When you need to ensure the connection is ACTIVE before running any workflows

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds
Step 2: Use RUBE_SEARCH_TOOLS to discover Woodpecker co tools and their schemas
Step 3: Connect with RUBE_MANAGE_CONNECTIONS, then execute a tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas and tool slugs
Check that the Woodpecker co connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before execution
Use exact field names and types from search results; avoid hardcoding slugs or args
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and handle pagination tokens when present

Example Use Cases

Automate a lead outreach campaign by discovering tools, authenticating, and executing a sequence of Woodpecker co tasks via Rube MCP
Run a multi-tool outreach workflow: discover tools, validate connection, execute tools with memory and session management
Fetch current tool schemas before each run to prevent failures from schema changes in Woodpecker co
Reuse a session ID to continue an ongoing Woodpecker co workflow across multiple tool executions
Handle paginated tool results by continuously calling RUBE_SEARCH_TOOLS until all pages are retrieved

Frequently Asked Questions

Add this skill to your agents