← LeaderboardThe Skill Leaderboard

buildkite-automation

Skill file composio-skills/buildkite-automation/SKILL.md in ComposioHQ/awesome-claude-skills. Read the publisher’s upstream source.

Description awaits a fresh source check.

Published by ComposioHQ ↗ComposioHQ/awesome-claude-skills

Try your first task

Start a fresh conversation. Replace the highlighted placeholders.

Use buildkite-automation to Complete [the specific Buildkite operation and required details] using [the existing Buildkite connection reference]. Require a connected Rube MCP and an active Buildkite connection, discover the current supported schema first, and return the operation result. If the supported operation would publish, purchase, destroy data, or change consequential settings, obtain my explicit confirmation immediately before executing it.

Required inputs

[the specific Buildkite operation and required details]
[the existing Buildkite connection reference]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: buildkite-automationdescription: "Automate Buildkite tasks via Rube MCP (Composio). Always search tools first for current schemas."requires:   mcp: [rube]

Buildkite Automation via Rube MCP

Automate Buildkite operations through Composio's Buildkite toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/buildkite

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Buildkite connection via RUBE_MANAGE_CONNECTIONS with toolkit buildkite
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 buildkite
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: "Buildkite 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 Buildkite task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["buildkite"]
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 Buildkite-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `buildkite`
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`