What prerequisites are required?

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) and an active Rootly connection via RUBE_MANAGE_CONNECTIONS with toolkit rootly.

Why must tools be discovered before execution?

Tool schemas change; discovering tools ensures you use current slugs and arguments.

What should be included in RUBE_MULTI_EXECUTE_TOOL calls?

Always include memory (even if empty) and use the exact field names/types from the tool schemas; reuse session IDs when possible.

rootly-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Rootly Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/rootly

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["rootly"]
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 Rootly-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `rootly`
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/rootly-automation/SKILL.mdView on GitHub

Overview

Automate Rootly operations using Composio's Rootly toolkit through Rube MCP. It emphasizes discovering current tool schemas first and managing Rootly connections before running workflows.

How This Skill Works

You connect to Rube MCP, search for current Rootly tool schemas with RUBE_SEARCH_TOOLS, verify the Rootly connection with RUBE_MANAGE_CONNECTIONS, then execute tools via RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and correct arguments. Always include memory in the execute call and reuse sessions where appropriate.

When to Use It

When automating a Rootly operation and tool schemas may change, so you must search first.
When establishing a new Rootly integration, verify and activate the RUBE MCP connection before running workflows.
When performing batch or repeatable Rootly tasks, use memory and session reuse for efficiency.
When you need the exact field names and types from the latest Rootly tool schemas.
When you want to avoid hardcoding tool slugs and rely on the discovered slugs from RUBE_SEARCH_TOOLS.

Quick Start

Step 1: Add the Rube MCP endpoint and confirm RUBE_SEARCH_TOOLS responds.
Step 2: Connect to the Rootly toolkit with RUBE_MANAGE_CONNECTIONS toolkits: ["rootly"] and ensure status is ACTIVE.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it with RUBE_MULTI_EXECUTE_TOOL using the memory object and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to get current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from the search results; do not hardcode slugs or arguments.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new ones only for new workflows; watch for pagination.

Example Use Cases

Discover Rootly tool slugs with RUBE_SEARCH_TOOLS and run a simple Rootly task using RUBE_MULTI_EXECUTE_TOOL.
Connect to the Rootly toolkit via RUBE_MANAGE_CONNECTIONS and execute multiple tools in a single workflow.
Retrieve tool schemas with RUBE_GET_TOOL_SCHEMAS and adapt arguments accordingly for a Rootly operation.
Handle pagination tokens while listing tools and continue fetching until complete.
Use RUBE_REMOTE_WORKBENCH to run composio tools in bulk for Rootly operations.

Frequently Asked Questions

Add this skill to your agents