alert
SkillTriage 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.
Install
git clone https://github.com/Rootly-AI-Labs/rootly-claude-plugin.git ~/.claude/skills/alertWhat is alert?
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.
What this can do
Capabilities declared in this component's own frontmatter — not inferred.
~56 tokens of context used while enabled, before you invoke anything
All declared tools (1)
mcp__rootly__*Trust
74/100 · Good3 factors scored below maximum
Documentation
README · ~2 min readAlert Triage
You are helping the user triage a Rootly alert. Alerts are the upstream signal that may or may not become incidents. The goal is to give the user enough context in one place that they can decide: ignore, acknowledge, escalate, or open an incident.
Workflow
1. Resolve the alert
$ARGUMENTS should contain a short alert ID (e.g. A-1234 or 1234).
- If
$ARGUMENTSis empty: report "No alert ID provided. Pass a short ID likeA-1234or1234." and stop. - Otherwise call
mcp__rootly__get_alert_by_short_idwith the value as given. - If that fails, fall back to
mcp__rootly__getAlertwith the same value (the MCP layer often accepts both forms). - If both fail, surface the error and stop.
2. Gather context
Reviews
Log in to leave a review.
No reviews yet — be the first.
Explore related
Other things in this space — across every part of the ecosystem, not just skills.
Skillssimilar to this one
All skills →cardputer-buddy
Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user wants to add a new app, push a single changed .py without re-flashing, watch device serial logs, or run a one-shot REPL command. Trigger on "add
32.8K stars
planning-with-files
Persistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Claude Code, Codex, Cursor, Kiro, OpenCode and 60+ agents via the Agent Skills standard.
25.8K stars
troubleshoot
Diagnose and fix a failing or misbehaving Atomic Agents app — import errors, schema validation failures, empty or malformed LLM output, provider role/mode errors, history and context problems, MCP transport errors. Use when the user reports an error, traceback, or wrong behavior in atomic-agents cod
6.1K stars
Plugins
All plugins →chrome-devtools-mcp
Control and inspect a live Chrome browser from your coding agent. Record performance traces, analyze network requests, check console messages with source-mapped stack traces, and automate browser actions with Puppeteer.
47.9K stars
deepeval
Skills for adding DeepEval evaluations, tracing, datasets, Confident AI reports, and iterative improvement loops to AI applications.
17.3K stars
aws-agents-for-devsecops
Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.
2.2K stars
MCP Servers
All mcp servers →monitor
BetterDB MCP server - Valkey observability for Claude Code and other MCP clients
1.2K stars
MikroMCP
MCP server for MikroTik RouterOS: typed tools, dry-run, RBAC, audit logs, and rollback.
42 stars
suitecrm-mcp
Open-source MCP gateway for SuiteCRM - 24 CRM tools, OAuth2/OIDC auth, multi-entity, observability.
1 stars
Subagents
All subagents →code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
32.8K stars
retro-analyst
Reliability pattern analyst for retrospectives, recurring-incident clustering, and systemic improvement recommendations.
1 stars
incident-investigator
Deep production-incident investigator for root-cause analysis, evidence gathering, and remediation planning beyond the initial response brief.
1 stars
Commands
All commands →help
Get help with FiftyOne skills, understand available workflows, and troubleshoot setup issues
32.8K stars
troubleshoot-connector
Troubleshoot ZPA App Connector issues -- enrollment, connectivity, upgrades, and resource utilization.
investigate-sandbox
Investigate ZIA Sandbox file analysis -- check sandbox reports, quota, SSL prerequisite, and diagnose file block/quarantine issues.