From devops-practices
SLO-based alerting, threshold tuning, incident escalation, runbooks, and on-call management.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devops-practices:alerting-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Effective alerts that wake up on-call engineers only for real problems.
Effective alerts that wake up on-call engineers only for real problems.
You are designing alerts. Alert on SLOs, not absolute thresholds; provide runbooks.
npx claudepluginhub sethdford/claude-skills --plugin engineer-devops-practicesWrites SLO-based alert rules with burn-rate thresholds and paired runbooks for Prometheus, Grafana, Datadog, CloudWatch. Outputs configs when asked to set up alerts, create runbooks, or define SLOs.
Write SLO-based alert rules with burn rate thresholds and paired runbooks. Outputs actual alert configs, not a strategy doc. Use when asked to "set up alerts", "create runbooks", "define SLOs", or "alerting strategy".
Designs monitoring systems: SLOs, uptime checks, error tracking, alert routing, on-call rotations. Use when setting up or fixing monitoring, alert fatigue, or incident gaps.