$ ~/registry/skill/composiohq-composio-skills-woodpecker-co-automation

SKILL

woodpecker-co-automation

Name: woodpecker-co-automation
Author: Composio

Automate Woodpecker CI tasks and workflow operations through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

Overall, this appears to be a prompt-only skill with no declared secrets and no declared remote endpoints, so the intrinsic risk is low. The main thing to note is that it operates via Rube MCP to reach an external service, which is a normal tool capability rather than a high-risk red flag.

CredentialsLow risk

No API keys, tokens, or environment variables are required in the materials; it only mentions managing connection status via Rube, with no explicit credential abuse or leakage risk.

Network egressCaution

No direct remote endpoint is listed; however, the README explicitly uses Rube MCP (e.g., rube.app/mcp) to interact with external services, implying normal task-related network egress.

Code executionCaution

The material only describes an MCP tool workflow and does not show local arbitrary code execution, process spawning, or system-level permission requests; this is tool invocation, not code execution.

Data accessCaution

It is expected to access Woodpecker co task data and session content, but there is no evidence of overbroad local file or resource access; the data boundary is mainly defined by the external tool.

Supply chainCaution

The source is GitHub with high community stars and open-source audibility, which are positive signals; however, the license is undeclared, maintenance status is unknown, and it depends on external Composio/Rube infrastructure, so supply-chain caution remains.

Recommendations

Use it only after confirming the authorization scope for Rube MCP and Woodpecker co.
Review the actual tool list and returned fields to avoid sending unnecessary data to external services.
For production use, verify the repository license, recent maintenance, and dependency updates.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "woodpecker-co-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/woodpecker-co-automation/SKILL.md
2. Save it as ~/.claude/skills/woodpecker-co-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Botpress tasks and workflow actions through Rube MCP.

ComposioGet→

$ loading_