Alerting config
Skill AtulPurohit/Antigravity-Awesome-Skills/skills/alerting-config
Installable GitHub library of 300+ professional agentic skills for Claude Code, Antigravity IDE, Gemini CLI, Cursor, and Copilot. Features a custom NPX installer, 9 stack-specific bundles, validation schemas, security auditing, and an interactive catalog explorer app.
npx -y skills add AtulPurohit/Antigravity-Awesome-Skills --skill alerting-configAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Design effective alerting that catches real issues and minimizes false alarms.
SKILL.md
2.4 KB, 511 tokens by cl100k_base, as published. Nobody here has run it
Alerting Configuration Expert
Purpose
Build alerting systems that notify engineers only for actionable, high-severity events.
Key Principles
- Every alert must be actionable
- Alert on symptoms (high latency) not causes (high CPU)
- Severity-appropriate routing
- SLO-based burn rate alerts (better than threshold alerts)
Prometheus Alert Rules
groups:
- name: slo.rules
rules:
- alert: HighErrorBudgetBurn
# Multi-window, multi-burn-rate alert
expr: |
(
rate(http_requests_total{status=~"5.."}[1h]) /
rate(http_requests_total[1h]) > 0.14
) and (
rate(http_requests_total{status=~"5.."}[5m]) /
rate(http_requests_total[5m]) > 0.14
)
for: 2m
labels:
severity: critical
team: backend
annotations:
summary: "Error rate {{ $value | humanizePercentage }} - burning error budget fast"
runbook: "https://wiki/runbooks/high-error-rate"
- alert: HighP99Latency
expr: histogram_quantile(0.99, rate(http_duration_seconds_bucket[5m])) > 1.0
for: 5m
labels:
severity: warning
annotations:
summary: "P99 latency is {{ $value | humanizeDuration }}"
AlertManager Routing
route:
group_by: [alertname, service]
group_wait: 30s
group_interval: 5m
repeat_interval: 12h
receiver: slack-default
routes:
- matchers: [severity=critical]
receiver: pagerduty-critical
continue: true
- matchers: [severity=warning]
receiver: slack-warnings
receivers:
- name: pagerduty-critical
pagerduty_configs:
- service_key: $PAGERDUTY_KEY
- name: slack-warnings
slack_configs:
- channel: '#alerts-warnings'
Outputs
- Alert rules for application and infrastructure
- AlertManager routing configuration
- Runbook template for each alert
- On-call schedule configuration
- Alert review process (monthly)