home / skills / composiohq / awesome-claude-skills / bugbug-automation

bugbug-automation skill

safe

/bugbug-automation

This skill automates Bugbug tasks via Rube MCP, always discovering current tool schemas before execution to ensure accurate workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill bugbug-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.8 KB

---
name: bugbug-automation
description: "Automate Bugbug tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Bugbug Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/bugbug](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bugbug`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Bugbug tasks through Composio's Bugbug toolkit using the Rube MCP orchestration layer. It provides a reliable pattern for discovering current tool schemas, validating connections, and executing Bugbug operations programmatically. The skill emphasizes dynamic tool discovery and schema compliance to avoid breaking changes.

How this skill works

First, the skill calls RUBE_SEARCH_TOOLS to fetch available Bugbug tools, their input schemas, and recommended execution plans. It then confirms an active Bugbug connection via RUBE_MANAGE_CONNECTIONS and runs operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, always passing a memory object and reusing session IDs for workflow continuity. The workflow enforces schema compliance and pagination handling returned by the MCP.

When to use it

Automating repetitive Bugbug tasks like labeling, triage, or batch analysis.
Integrating Bugbug operations into larger CI/CD or agent workflows.
When tool schemas may change frequently and you need robust discovery.
Running bulk or remote workbench jobs that rely on Composio toolchains.
Orchestrating multi-step Bugbug flows that require session state.

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or arguments.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the bugbug toolkit before executing tools.
Pass a memory object (can be empty {}) in RUBE_MULTI_EXECUTE_TOOL calls.
Reuse session IDs within a workflow; generate new session IDs for new workflows.
Respect exact field names and types from returned schemas and handle pagination tokens.

Example use cases

Discover available Bugbug analyzers and run a batch defect scan across repositories.
Automate triage: fetch issues, classify with Bugbug, and update labels via multi-execute.
Run a remote workbench job to process large datasets with run_composio_tool() and aggregate results.
Embed Bugbug operations into an agent pipeline that pre-validates schema and connection state.

FAQ

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client configuration.

What if a tool schema changes during a workflow?

Call RUBE_SEARCH_TOOLS again to refresh schemas, update arguments to match exact fields and types, and continue with the updated session.