Ask

by Rootly-AI-Labs65832aa6ff7aNo licenseListed Oct 8, 2026Updated Oct 8, 2026

Ask natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers.

Instructions onlyDevOps & Cloud
AI-generated overview

Answers natural language questions about incidents, on-call, and reliability data by querying Rootly's MCP tools.

What it does
This instruction-only skill takes a user's natural language question about incidents, on-call schedules, services, or reliability data and translates it into Rootly API calls through Rootly MCP tools. It first lists available endpoints, then selects and runs the appropriate queries, possibly several, and returns a structured answer with supporting data and source attribution. It also states clearly when a question falls outside the data Rootly provides.
When to use it
Use it when someone wants a quick answer about incident counts, on-call coverage, service-related incidents, severity filtering, or patterns in failures without writing API queries themselves. It fits reliability and on-call workflows where Rootly is the system of record.
Requirements
Requires access to Rootly MCP tools (mcprootly*) and the underlying Rootly account and credentials. It ships no scripts; it is instructions only.

Natural Language Query

You are answering a natural language question about the user's incident, on-call, or reliability data using Rootly's MCP tools.

Workflow

1. Understand the Question

Parse the user's question from $ARGUMENTS. Identify what data they need.

2. Discover Available Tools

Call mcp__rootly__list_endpoints to see the full list of available Rootly MCP tools and their capabilities. This helps you select the right tools for the query.

3. Execute Queries

Select the most appropriate tools for the question. You may need multiple calls to fully answer the question. Common patterns:

  • "How many incidents last week?" -> mcp__rootly__search_incidents with date filters
  • "Who's on call?" -> mcp__rootly__get_oncall_handoff_summary
  • "What happened with [service]?" -> mcp__rootly__search_incidents filtered by service
  • "Show me critical incidents" -> mcp__rootly__search_incidents filtered by severity
  • "Any patterns in auth service failures?" -> mcp__rootly__search_incidents + mcp__rootly__find_related_incidents

4. Present Answer

Provide a clear, structured answer with supporting data. Include:

  • Direct answer to the question
  • Supporting data in tables or lists where helpful
  • Source attribution (which tools/queries produced the data)

5. Limitations

Be explicit about what you can't answer. If the question requires data that isn't available through the Rootly MCP tools, say so clearly rather than guessing or hallucinating. For example:

  • "I can't answer questions about infrastructure metrics -- Rootly tracks incidents, not system metrics."
  • "This question requires data from [other system]. I can only query Rootly incident and on-call data."

Source and attribution

Source:Rootly-AI-Labs/rootly-claude-plugininskills/askat commit65832aa

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal