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

bugherd-automation skill

safe

/bugherd-automation

This skill automates Bugherd operations via Rube MCP, always discovering current tool schemas to ensure reliable, up-to-date task execution.

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

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

Files (1)

SKILL.md

2.9 KB

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

# Bugherd Automation via Rube MCP

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

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

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bugherd`
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: "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](https://composio.dev)*

Overview

This skill automates Bugherd tasks by orchestrating Composio's Bugherd toolkit through a Rube MCP connection. It provides a repeatable pattern for discovering tools, validating connections, and executing operations while ensuring schema compliance and session management. Use it to run single actions or bulk workflows against Bugherd without hardcoding tool details.

How this skill works

The skill first queries RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and recommended execution plans for Bugherd operations. It validates that a Bugherd connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, then calls RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk tasks) with schema-compliant arguments and an explicit memory object. Sessions are reused for related workflows and new sessions generated for distinct runs.

When to use it

Create, update, or triage Bugherd tickets programmatically.
Run repeatable QA or triage workflows that must respect live tool schemas.
Perform bulk updates or exports via RUBE_REMOTE_WORKBENCH and composio tooling.
Integrate Bugherd operations into larger agent-led automation flows.
When you need reliable schema-driven execution without hardcoding APIs.

Best practices

Always call RUBE_SEARCH_TOOLS first to get the current tool schema and slug before executing anything.
Verify Bugherd connection status with RUBE_MANAGE_CONNECTIONS and complete any auth flows until status is ACTIVE.
Pass an explicit memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls and reuse session IDs within a workflow.
Use RUBE_GET_TOOL_SCHEMAS when you need the full schema_ref for complex inputs or validation.
Handle pagination tokens in responses and continue fetching until results are complete.

Example use cases

Discover the create-issue tool, validate connection, and create a Bugherd issue with schema-validated fields.
Bulk update issue statuses using RUBE_REMOTE_WORKBENCH and run_composio_tool() across many tickets.
Fetch available Bugherd tooling, extract required input schemas, and generate a form for user input in a UI.
Automate triage: search tools, run a sequence that labels, assigns, and comments on tickets in one session.

FAQ

Do I need API keys to use Rube MCP?

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

What if a tool schema changes after I built my workflow?

Always re-run RUBE_SEARCH_TOOLS at workflow start. Never hardcode slugs or argument shapes; adapt to the returned schema and field types.