$ ~/registry/skill/composiohq-composio-skills-bugbug-automation

SKILL

bugbug-automation

Name: bugbug-automation
Author: Composio

Automate BugBug tasks through Rube MCP to streamline testing workflows.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself appears to be an open-source prompt-only wrapper with strong community adoption and no direct local secret requirement, so the baseline risk is low. However, it depends on external Rube MCP/Composio and a Bugbug connection, which introduces network egress and third-party execution paths that should be verified during actual deployment.

CredentialsCaution

The material says there are 'no API keys', but it also requires an ACTIVE Bugbug connection via RUBE_MANAGE_CONNECTIONS and an auth-link flow, which suggests credentials are likely delegated to an external platform rather than absent. No explicit credential theft behavior is described, but third-party connection authorization still creates token management and misuse exposure.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint https://rube.app/mcp and performing operations through Composio/Bugbug, so task content, arguments, and potentially business data will be sent to the declared third-party services. The endpoint is stated and functionally relevant, making this routine egress rather than a red flag, but the material does not specify data minimization or retention details.

Code executionLow risk

The system flags this as prompt-only, and the content mainly provides workflow guidance and call sequencing without asking users to download, install, or execute local scripts/binaries, nor does it request extra system privileges. Based on the provided material, no local code-execution surface is evident.

Data accessCaution

This skill performs Bugbug 'operations' through an external toolchain and even supports bulk operations and a remote workbench; while it does not claim direct local file access, it can access data and resources exposed through the user's Bugbug/Composio authorization. The material does not define least-privilege boundaries or exact data scope, so the granted access should be reviewed at connection time.

Supply chainLow risk

The source is an open GitHub repository, and the system provides strong positive signals via open-source status and high community trust (64.7k stars), which supports auditability and source credibility. The license and maintenance status are not explicit, and full functionality depends on external Rube/Composio services, so upstream terms and changes should still be reviewed, but this is not enough on its own to warrant a high-risk rating.

Recommendations

Before adoption, verify data flows, logging retention, and privacy terms across rube.app, Composio, and Bugbug.
Use a least-privilege Bugbug account during authorization and expose only the resources needed for the intended automation.
Validate the real callable capabilities of RUBE_SEARCH_TOOLS / RUBE_MULTI_EXECUTE_TOOL in a test environment before allowing bulk operations.
Track and periodically review external connection status and granted tokens, and remove integrations that are no longer needed.

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 "bugbug-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/bugbug-automation/SKILL.md
2. Save it as ~/.claude/skills/bugbug-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Honeybadger tasks through Rube MCP with schema lookup first.

ComposioGet→

$ loading_