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

SKILL

bugherd-automation

Name: bugherd-automation
Author: Composio

Automate BugHerd tasks to streamline bug tracking and team workflows.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

The material appears to be an open-source prompt/instruction skill with no direct local execution or explicit secret collection, so overall risk is low. However, its actual workflow depends on external Rube MCP and Bugherd/Composio connectivity, which introduces third-party authorization and data egress considerations.

CredentialsCaution

The material claims “no API keys needed,” but it explicitly requires an active Bugherd connection via `RUBE_MANAGE_CONNECTIONS` and following a returned auth link, indicating reliance on third-party account tokens/OAuth sessions. The skill itself does not directly collect secrets, but normal delegated-credential risk exists through Rube/Composio-mediated Bugherd authorization.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and performing operations through Composio's Bugherd toolkit. This implies task content, arguments, and Bugherd-related data are sent to external services. The egress targets are related to the stated functionality, with no clear unrelated or hidden endpoints, so this is a caution rather than a high-risk finding.

Code executionLow risk

The objective checks mark it as prompt-only, and the material does not declare starting local processes, executing scripts, or requesting system-level capabilities. While it discusses invoking remote MCP tools, the skill material itself does not grant direct local code-execution capability.

Data accessCaution

The material does not show local file reads or host data access; its data-access surface is mainly authorized Bugherd resources plus task parameters and session information sent through `RUBE_SEARCH_TOOLS`/`RUBE_MULTI_EXECUTE_TOOL`. The scope is broadly consistent with the stated Bugherd automation purpose, but connections should still be limited to the minimum necessary account/project scope.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk. The material is also marked open-source and prompt-only, making it easier to review. Caveats remain: the license is unspecified, maintenance status is unknown, and it depends on external Rube/Composio services, so ongoing changes should still be monitored.

Recommendations

Authorize only if you trust the Rube/Composio and Bugherd integration path, and prefer minimum-privilege Bugherd accounts scoped to the smallest necessary projects.
Review what your client sends to `rube.app/mcp` and avoid placing unrelated sensitive data into tool arguments or session memory.
Verify repository maintenance, release history, and upstream documentation before enabling it, and account for the missing license from a compliance perspective.
If possible, validate `RUBE_SEARCH_TOOLS`, the connection flow, and actual data visibility in a test project before using it in a production workspace.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Bugherd Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bugherd

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["bugherd"]
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 Bugherd-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `bugherd`
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 Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_