bugsnag-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/bugsnag-automation --openclawBugsnag Automation via Rube MCP
Automate Bugsnag operations through Composio's Bugsnag toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/bugsnag
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bugsnag connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbugsnag - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitbugsnag - 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: "Bugsnag 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 Bugsnag task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["bugsnag"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Bugsnag-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit bugsnag |
| 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/bugsnag-automation/SKILL.mdView on GitHub Overview
Automate Bugsnag operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running workflows to prevent stale integrations, and requires an ACTIVE Bugsnag connection via RUBE_MANAGE_CONNECTIONS with the 'bugsnag' toolkit.
How This Skill Works
Start by discovering available tools with RUBE_SEARCH_TOOLS using a Bugsnag use_case. Then verify the connection with RUBE_MANAGE_CONNECTIONS and execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, passing the required memory payload. The workflow follows: 1) Discover tools, 2) Check connection, 3) Execute tools, reusing session IDs as needed.
When to Use It
- When you need to perform a Bugsnag operation and want up-to-date tool schemas from Rube MCP before execution
- When you must verify that the Bugsnag connection is ACTIVE before running workflows
- When you want to discover available Bugsnag tools for a specific task
- When executing one or more tools in sequence using RUBE_MULTI_EXECUTE_TOOL (including memory payloads)
- When reusing session IDs across a workflow and handling pagination tokens from tool discovery
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit: ["bugsnag"] and confirm ACTIVE status
- Step 3: Use RUBE_SEARCH_TOOLS to discover a Bugsnag task, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and memory: {}
Best Practices
- Always call RUBE_SEARCH_TOOLS before running to fetch current tool slugs and schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
- Use exact field names and types from the search results; avoid hardcoding slugs or arguments
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
- Reuse session IDs within a workflow and manage pagination tokens to fetch complete tool lists
Example Use Cases
- Discover Bugsnag tools, connect via the bugsnag toolkit, then run a specific Bugsnag operation with its required arguments
- Execute multiple Bugsnag tasks in a batch using RUBE_MULTI_EXECUTE_TOOL while maintaining a single session_id
- Retrieve current tool schemas with RUBE_SEARCH_TOOLS, then adapt a workflow to updated inputs without manual changes
- Ensure MCP server is configured (https://rube.app/mcp) and test connectivity with RUBE_SEARCH_TOOLS before automation
- Handle pagination in tool discovery responses and continue fetching until all tools are retrieved
