From rootly
Ask natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rootly:askThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are answering a natural language question about the user's incident, on-call, or reliability data using Rootly's MCP tools.
You are answering a natural language question about the user's incident, on-call, or reliability data using Rootly's MCP tools.
Parse the user's question from $ARGUMENTS. Identify what data they need.
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.
Select the most appropriate tools for the question. You may need multiple calls to fully answer the question. Common patterns:
mcp__rootly__search_incidents with date filtersmcp__rootly__get_oncall_handoff_summarymcp__rootly__search_incidents filtered by servicemcp__rootly__search_incidents filtered by severitymcp__rootly__search_incidents + mcp__rootly__find_related_incidentsProvide a clear, structured answer with supporting data. Include:
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:
claude plugin install rootly@claude-plugins-officialGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.