Woodpecker Co Automation

What This Skill Does

This skill automates operations within Woodpecker co using the Composio Woodpecker co toolkit via Rube MCP. It is designed for users who need to manage and automate tasks within the Woodpecker co platform. The skill ensures proper setup and tool discovery for efficient workflow execution.

When to Use

• Automate Woodpecker co tasks.
• Discover available Woodpecker co tools.
• Check Woodpecker co connection status.
• Execute Woodpecker co tools.
• Search for specific Woodpecker co tasks.
• Manage Woodpecker co connections.

Key Features

• Uses Rube MCP for Woodpecker co automation.
• Requires active Woodpecker co connection.
• Employs RUBE_SEARCH_TOOLS for tool discovery.
• Provides a core workflow pattern for execution.
• Highlights the importance of schema compliance.
• Offers setup instructions for Rube MCP.

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