rootly-automation

Automate Rootly tasks via Rube MCP (Composio). Always search tools first for current schemas.

Install

Hot:35

Download and extract to your skills directory

Copy command and send to AI Agent for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-rootly-automation&locale=en&source=copy

Rootly Automation Skill

Skill Overview


Automate Rootly incident management operations via the Rube MCP, supporting incident response, workflow triggering, and bulk processing. Quickly integrate without requiring an API key.

Use Cases

  • Incident Response Automation: Automatically create Rootly incidents, update incident states, and send notifications to team communication channels to accelerate the incident response process.
  • Bulk Operations and Workflows: Perform bulk updates in Rootly, trigger automation workflows, and generate incident reports—reducing repetitive manual work.
  • Incident Management and Integration: Connect to the Rootly API through MCP to integrate into existing DevOps toolchains, enabling end-to-end incident management automation.
  • Core Capabilities

  • MCP Tool Discovery and Connection: Discover available Rootly tools and functions via RUBE_SEARCH_TOOLS, and manage Rootly API connection status using RUBE_MANAGE_CONNECTIONS.
  • Executing Rootly Operations: Supports executing Rootly tasks such as incident creation, updates, and queries through RUBE_MULTI_EXECUTE_TOOL, automatically handling input schemas and session management.
  • Bulk and Advanced Operations: Use RUBE_REMOTE_WORKBench for complex Rootly bulk processing, supporting paginated queries and full schema retrieval.
  • FAQs

    What prerequisites are required for the Rootly automation skill?


    You need Rube MCP to be connected (add https://rube.app/mcp as the MCP server) and establish an active connection to Rootly via RUBE_MANAGE_CONNECTIONS. For the first use, follow the returned authentication link to complete authorization.

    How do I discover available Rootly tools?


    Always call RUBE_SEARCH_TOOLS first, passing a Rootly-related use_case query. It will return the currently available tool slugs, input schemas, and execution plans. Do not hard-code tool names, as schemas may change.

    What are common errors when executing Rootly operations?


    Common errors include: skipping tool search and executing directly, failing to verify the connection status is ACTIVE, input parameters not matching the current schema, and forgetting to include the memory parameter. It’s recommended that for every workflow you first search for tools, then check the connection, and finally execute the operation.