Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Better Stack Automation via Rube MCP

agent tool_use skill risk: medium

Better Stack Automation via Rube MCP

Instructs the model to automate Better Stack operations through Composio's toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, then RUBE_MANAGE_CONNECTIONS to verify ACTIVE st…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: better-stack-automation
description: "Automate Better Stack tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Better 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](https://composio.dev/toolkits/better_stack)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Better Stack connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `better_stack`
- 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 `better_stack`
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: "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_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 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • Better Stack toolkit connection

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit better_stack
  5. If connection is not ACTIVE, follow the returned auth link to complete setup
  6. Confirm connection status shows ACTIVE before running any workflows
  7. Always discover available tools before executing workflows
  8. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  9. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  10. Use exact field names and types from the search results
  11. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  12. Reuse session IDs within a workflow
  13. Generate new ones for new workflows
  14. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify connection status before execution
  • reuse session IDs within workflows

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Better Stack connection via RUBE_MANAGE_CONNECTIONS with toolkit better_stack
Missing context
  • Target AI model or client (e.g., Claude, GPT)
  • Example concrete use cases or sample task inputs
  • Error handling or fallback behavior expectations
Ambiguities
  • Placeholders like "your specific Better Stack task" and "TOOL_SLUG_FROM_SEARCH" are not fully defined for direct substitution.
  • Does not specify desired output length or response format when executing workflows.

QUALITY

OVERALL
0.76
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.68
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Replace inline code blocks with explicit {{placeholder}} syntax for session_id, use_case, and tool arguments to improve reusability.
  • Add a short 'Success Criteria' section defining what a completed workflow looks like.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT