alerting-rules-agent

Generate Prometheus alert rules and PagerDuty routing configurations.

Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Unicorn/Radium --skill alerting-rules-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alerting-rules-agent
Source: https://github.com/Unicorn/Radium/tree/main/skills/devops/alerting-rules-agent
Command: npx skills add https://github.com/Unicorn/Radium --skill alerting-rules-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces missed incidents and alert fatigue by designing actionable alerting rules, sensible thresholds, and reliable routing so teams are notified of real problems without being overwhelmed by noise.

Core Features & Use Cases

  • Alert strategy design: Identify key signals, define SLO-driven thresholds, and map severity levels to business impact.
  • Rule configuration: Produce Prometheus-style alerting rules, time windows, and aggregation to avoid flapping and false positives.
  • Routing & escalation: Map severities to PagerDuty/Opsgenie policies, define escalation policies, and set urgency/timeouts.
  • On-call & suppression: Design on-call rotations, suppression windows, grouping, and dependencies to prevent cascades.
  • Runbooks & testing: Create runbooks for common alerts and define testing procedures to validate delivery and escalation.
  • Use Case: Create Prometheus alerts and PagerDuty routing for an API service with a 99.9% availability SLO to prioritize critical outages while minimizing noisy warnings.

Quick Start

Create Prometheus alerting rules for the API service with a 99.9% availability SLO, mapping critical errors to the platform on-call and grouping noisy transients.

Frequently Asked Questions about alerting-rules-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Prometheus alerting rules to reduce alert noise and prevent flapping?

Configure Prometheus alerting rules by defining SLO-driven thresholds, applying time windows, and aggregating metrics to reduce alert noise and prevent flapping. This approach ensures notifications are timely and actionable without overwhelming on-call teams.

What is the best way to route critical Prometheus alerts to PagerDuty or Opsgenie?

Route critical Prometheus alerts by mapping severity levels to PagerDuty or Opsgenie escalation policies. Define escalation timeouts and urgency levels to ensure critical outages reach the platform on-call team quickly while suppressing noisy transients.

How do I design on-call schedules and suppression windows for incident management?

Design on-call schedules and suppression windows by configuring routing dependencies and grouping strategies. This prevents cascading alerts during major incidents and ensures that defined escalation policies notify the correct responders without alert fatigue.

Can I use this approach to generate alert rules for an API service with a 99.9% availability SLO?

Yes, you can generate alert rules for an API service with a 99.9% availability SLO. The configuration maps critical errors to on-call policies, prioritizes real outages, and minimizes noisy warnings based on latency, error rate, and infrastructure metrics.

How do I create runbooks and testing procedures for common monitoring alerts?

Create runbooks and testing procedures for common alerts alongside the alerting rule configuration. Define validation steps to test alert delivery and escalation paths, ensuring your incident management routing and suppression strategies work before a real outage.