How do I ensure tool schemas are current?

Always call RUBE_SEARCH_TOOLS before executing; do not hardcode tool slugs or arguments. Use the latest schemas returned by the search.

How can I tell if the Bugbug connection is active?

Use RUBE_MANAGE_CONNECTIONS with toolkits: ['bugbug'] and verify that the session shows ACTIVE before running workflows.

What should I include in memory for tool execution?

Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty, by passing memory: {} to preserve context within the session.

bugbug-automation

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

Files (1)

SKILL.md

2.8 KB

Bugbug Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bugbug

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["bugbug"]
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 Bugbug-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `bugbug`
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/bugbug-automation/SKILL.mdView on GitHub

Overview

Automate Bugbug operations through Composio's Bugbug toolkit using Rube MCP. It emphasizes discovering current tool schemas first and validating the connection before executing workflows, ensuring resilient and up-to-date automation.

How This Skill Works

Technically, you connect to Rube MCP, call RUBE_SEARCH_TOOLS to fetch current Bugbug tool schemas, and pick a tool slug. Then confirm the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS and run the tool via RUBE_MULTI_EXECUTE_TOOL, supplying the required inputs, memory, and session_id. Always refetch schemas to avoid hardcoded slugs.

When to Use It

When you need to automate a Bugbug operation with up-to-date tool schemas fetched from RUBE_SEARCH_TOOLS
When you must verify the Bugbug connection is ACTIVE before running workflows
When you want to discover the exact tool slug and input schema before execution
When chaining multiple Bugbug steps in a single workflow within one session
When you need to ensure memory is included in multi-tool execution calls

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds
Step 2: Discover available Bugbug tools with RUBE_SEARCH_TOOLS for use_case 'Bugbug operations' and start a session (session: {generate_id: true})
Step 3: Check the connection with RUBE_MANAGE_CONNECTIONS and execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory: {} and the active session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any Bugbug workflow
Verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from the search results (do not hardcode slugs)
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Automate creating a Bugbug task by discovering a tool slug with RUBE_SEARCH_TOOLS and invoking it with RUBE_MULTI_EXECUTE_TOOL
Run a Bugbug triage/assignment workflow by chaining multiple tools in a single session
Sync Bugbug statuses to an external tracker by executing a tool with the appropriate arguments
Validate tool schemas dynamically before each run to avoid hardcoding slugs
Reuse a session across multiple Bugbug steps to optimize workflow execution

Frequently Asked Questions

Add this skill to your agents