76 tagged alerting, measured the same way as everything else here.
Browse within: monitoring 44observability 34grafana 33metrics 31datadog 23time-series 23nightingale 22tsdb 22ai-sre 20remediation 20internal 16prometheus 15cli 13aiops 9
Skill Claude CodeCodex
This skill should be used when the user reports that an alert rule is "not firing", "no alert was sent", "the rule didn't trigger", "the rule isn't working", "it should have alerted but didn't", "why didn't I get an alert", "alert rule not firing", or wants to diagnose why a specific alert rule failed to produce an…
Skill Claude CodeCodex
Computes a CI/CD metrics table from raw GitHub Actions records for one repository over the last 30 days, including failure rates and developer waiting time. Use for historical CI performance questions or the first-experience repository demo. For currently failing checks, use reporting-github-ci-failures.
Skill Claude Code
A read-only shell skill for examining files and running diagnostic commands in a restricted environment. A shell is a text interface for operating-system commands.
Skill Claude Code
Point the ilert CLI at a staging, preview or self-hosted ilert environment by giving it its own profile.
Skill Claude CodeCodex
Explain why a Zabbix alert did or did not arrive. Use when asked why there was no notification, why an alert was missed, why a problem was not reported, or to trace notification delivery for an event.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: