What is honeybadger-automation?

A skill to automate Honeybadger tasks using Composio's Rube MCP toolkit, with live tool schemas fetched prior to execution.

Why must we search tools first?

Tool schemas change over time; RUBE_SEARCH_TOOLS returns current slugs and input schemas to prevent failures.

What should be included in the memory parameter?

Include memory in every RUBE_MULTI_EXECUTE_TOOL call (even if empty) to maintain session context and support stateful workflows.

honeybadger-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Honeybadger Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/honeybadger

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["honeybadger"]
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 Honeybadger-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `honeybadger`
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/honeybadger-automation/SKILL.md

View on GitHub

Overview

Honeybadger Automation via Rube MCP lets you orchestrate Honeybadger operations using Composio's Rube MCP toolkit. Always fetch live tool schemas with RUBE_SEARCH_TOOLS before workflows to adapt to changes. The pattern covers discovery, connection validation, and safe execution of Honeybadger tasks.

How This Skill Works

Connect to the Rube MCP server and ensure RUBE_SEARCH_TOOLS returns current tool schemas. Discover available Honeybadger tools for your task, validate an ACTIVE Honeybadger connection with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including memory and session_id as required.

When to Use It

Discover tools for a specific Honeybadger task and execute it in a single session.
Verify and establish an ACTIVE Honeybadger connection before running any workflows.
Always fetch current tool schemas to adapt to changes before automation.
Execute multiple Honeybadger tools in one run using RUBE_MULTI_EXECUTE_TOOL.
Reuse a session across related steps and handle pagination when discovering tools.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and ensure RUBE_SEARCH_TOOLS is available.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["honeybadger"] and verify the connection is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover a tool slug for your task, then run RUBE_MULTI_EXECUTE_TOOL with that slug and memory: {} in a new session.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
Reuse session IDs within a workflow and generate new ones for separate workflows; watch for pagination tokens.

Example Use Cases

Example 1: Discover tools for an incident triage task, verify the Honeybadger connection is ACTIVE, then run the chosen tool in a single session.
Example 2: Fetch the latest tool schemas, connect to Honeybadger via RUBE_MANAGE_CONNECTIONS, and execute a batch of monitors using RUBE_MULTI_EXECUTE_TOOL.
Example 3: Trigger a multi-step remediation workflow by discovering tools, validating connection, and executing multiple tools within one session with memory context.
Example 4: Regularly refresh tool schemas with RUBE_SEARCH_TOOLS before scheduled automations to avoid broken slugs or schemas.
Example 5: Retrieve the full tool schemas via RUBE_GET_TOOL_SCHEMAS and use schemaRef to ensure precise input mapping in executions.

Frequently Asked Questions

Add this skill to your agents