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

SKILL

honeybadger-automation

Name: honeybadger-automation
Author: Composio

Automate Honeybadger tasks through Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be an open-source prompt-style wrapper with no declared built-in secrets or local execution, and its high community adoption lowers overall risk. However, it depends on remote Rube MCP and a Honeybadger connection, so actual data egress and operational privileges are determined by the underlying MCP and third-party integration and should be verified before use.

CredentialsCaution

The material says the skill itself needs no API keys, but it explicitly requires an active Honeybadger connection via `RUBE_MANAGE_CONNECTIONS` and an auth-link flow, which means third-party account authorization/tokens are still involved. Not configuring secrets inside the skill reduces direct exposure, but the scope and storage of underlying connection credentials are not described.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to search tools, manage connections, and execute Honeybadger operations. This implies task arguments, session IDs, and potentially Honeybadger-related data are sent to a declared third-party service. The endpoint is identified and functionally relevant, with no obvious signs of unrelated or covert exfiltration.

Code executionLow risk

The system marks it as `prompt-only`, and the material does not describe local script execution, install commands, shell invocation, or requests for extra system privileges. This skill appears to be usage guidance for external MCP tools rather than a component that directly executes code on the local machine.

Data accessCaution

The skill does not claim direct read/write access to local files or system data, but it does perform actions against Honeybadger through Rube/Composio and requires session reuse plus a `memory` parameter. Therefore, its accessible data scope includes at least user-provided Honeybadger task context and any resources visible to the connected account. No local over-privilege is shown, but remote business-data access should be governed by Honeybadger connection scopes.

Supply chainLow risk

The source is an open-source GitHub repository, and the system reports `open-source` plus strong community adoption (64.7k stars), both of which are meaningful risk-reducing signals. The material shows no closed-source distribution, suspicious install scripts, or mismatched endpoints; remaining gaps are the undeclared license and unknown maintenance status, which should be checked before production use.

Recommendations

Before connecting, verify the data-handling and authorization scope of `rube.app/mcp` and Composio/Honeybadger, and grant only the minimum required permissions.
Avoid sending unnecessary sensitive data in tool-search prompts, session memory, or execution arguments.
Use a test or low-privilege Honeybadger account first to validate available tools and real operational impact.
Before production use, review repository maintenance activity, commit history, and license status.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

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

Automate Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_