better-stack-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/better-stack-automation --openclawBetter Stack Automation via Rube MCP
Automate Better Stack operations through Composio's Better Stack toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/better_stack
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Better Stack connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbetter_stack - 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 toolkitbetter_stack - 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: "Better Stack 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 Better Stack task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["better_stack"]
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 Better Stack-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit better_stack |
| 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/better-stack-automation/SKILL.mdView on GitHub Overview
Automate Better Stack operations through Composio's toolkit via Rube MCP. The workflow coordinates discovering current tool schemas, validating an active Better Stack connection, and executing tools in a repeatable process. Always fetch current schemas with RUBE_SEARCH_TOOLS before running anything.
How This Skill Works
First, discover available tools using RUBE_SEARCH_TOOLS with a Better Stack use_case. Then, verify the Better Stack connection is ACTIVE via RUBE_MANAGE_CONNECTIONS for the toolkit better_stack. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory (even if empty) and the session_id from the workflow.
When to Use It
- You need to automate a repeating Better Stack task without hardcoding tool slugs.
- Tool schemas frequently change and you must fetch them fresh before execution.
- You want to verify the Better Stack connection is ACTIVE before running workflows.
- You're performing bulk or multi-tool execution using a discovered tool.
- You want to reuse a session ID within a workflow to maintain continuity.
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: better_stack and confirm ACTIVE.
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then run RUBE_MULTI_EXECUTE_TOOL with a discovered slug and memory: {}.
Best Practices
- Always run RUBE_SEARCH_TOOLS before executing any tool to get current schemas.
- Ensure RUBE_MANAGE_CONNECTIONS reports ACTIVE before tool execution.
- Use exact field names and types from search results; do not hardcode slugs or arguments.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({ }).
- Reuse session IDs within a workflow and avoid creating new ones unless necessary.
Example Use Cases
- Create an incident in Better Stack when a monitoring alert triggers.
- Bulk-update alert configurations across several projects using discovered tools.
- Synchronize incident statuses across teams as part of a nightly automation run.
- Backfill alert configurations by applying tool operations discovered at runtime.
- Re-run a previous task by reusing a session_id in a new workflow.
