القائمة
Ask natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Set up the Rootly plugin. Verifies MCP server connection via OAuth2 or API token and guides through configuration. Run this after installing the plugin.
Manage incident action items from the terminal. Subcommands - list (default - your open action items) or add <incident> "<summary>" (create one on an incident). Use to capture follow-ups during or after an incident without opening the Rootly UI.
Draft a stakeholder-facing status update for an active incident, then post it after explicit confirmation. Useful for incident commanders pushing public-status-page or internal updates without opening the Rootly UI. Write action - never posts without confirming.
Offer to cover someone else's on-call shift. Lists upcoming shifts on a team or schedule and creates an override placing you on the chosen one after explicit confirmation. Write action - never executes without confirming.
Request someone to cover one of your upcoming on-call shifts. Lists your shifts, helps identify a candidate based on availability, and creates an override after explicit confirmation. Write action - never executes without confirming.
Triage a Rootly alert by short ID. Pulls the alert record, its event timeline, related alerts in the same group, and any incident the alert is attached to. Use when a page comes in and you want context before opening Rootly.
| name | ask |
| description | Ask natural language questions about incidents, on-call, services, and reliability data. Translates your question into Rootly API calls and returns structured answers. |
| argument-hint | ["your question"] |
| disable-model-invocation | true |
| allowed-tools | ["mcp__rootly__*"] |
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: