rootly-automation

Automate incident management tasks and Rootly operations through the Rube MCP gateway.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill rootly-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rootly-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/rootly-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill rootly-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the friction of manual incident response by providing a standardized, automated interface for interacting with Rootly, ensuring consistent incident tracking and communication.

Core Features & Use Cases

  • Tool Discovery: Dynamically fetch current Rootly tool schemas and execution plans via Rube MCP.
  • Connection Management: Verify and maintain active authentication states for Rootly integrations.
  • Workflow Execution: Execute multi-step incident workflows, such as creating incidents or updating status pages, using validated tool schemas.

Quick Start

Use the rootly-automation skill to search for available tools and execute an incident update workflow.

Frequently Asked Questions about rootly-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Rootly tools?

Call the RUBE_SEARCH_TOOLS command with a query related to your specific Rootly task. This returns the current tool slugs, input schemas, and recommended execution plans for your session.

What should I do if my Rootly connection is inactive?

Run the RUBE_MANAGE_CONNECTIONS command with the rootly toolkit specified. If the status is not ACTIVE, follow the provided authentication link to re-authorize your connection.

Can I hardcode tool slugs in my workflows?

No, you should never hardcode tool slugs or arguments. Tool schemas change frequently, so always call RUBE_SEARCH_TOOLS first to retrieve the most current definitions.

Why must I include a memory parameter in tool calls?

The RUBE_MULTI_EXECUTE_TOOL requires a memory parameter to maintain state across operations. Even if you have no specific state to pass, you must include an empty object {} to ensure schema compliance.

How do I handle complex Rootly workflows?

Use RUBE_MULTI_EXECUTE_TOOL for standard operations or RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk operations. Always reuse session IDs within a single workflow to maintain context.