Alerting Strategy

SLO-based alerting, threshold tuning, incident escalation, runbooks, and on-call management.

48 stars 10 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill alerting-strategy
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/devops-practices/skills/alerting-strategy ~/.claude/skills/alerting-strategy

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Alerting Strategy

Effective alerts that wake up on-call engineers only for real problems.

## Context

You are designing alerts. Alert on SLOs, not absolute thresholds; provide runbooks.

## Domain Context

- **SLO**: Service level objective; what level of service do you promise?
- **Error Budget**: How much downtime/errors before violating SLO?
- **Alert Fatigue**: Too many alerts → on-call ignores them
- **Runbook**: Step-by-step guide to respond to alert
- **Escalation**: If on-call doesn't respond, escalate

## Instructions

1. **Define SLOs**: What do you commit to? 99.9% uptime?
2. **Measure Error Budget**: How much can you fail before SLO breach?
3. **Alert on SLO**: Alert when error budget is at risk
4. **Runbooks**: Document response for each alert
5. **Tuning**: Adjust thresholds to reduce false positives
6. **Escalation**: If on-call unresponsive, page manager
7. **Blameless Postmortems**: Learn from incidents, improve systems

## Anti-Patterns

- Alert on everything; alert fatigue kills response
- Alerts with no runbook; on-call is helpless
- SLO not communicated; customers expect unlimited uptime
- Static thresholds; day/night, weekday/weekend are different
- No escalation; on-call doesn't see alert

## Further Reading

- Google SRE book on monitoring and alerting
- SLO guidance (Google Cloud)
- PagerDuty on-call best practices
Read the full skill on GitHub

Details

Skill name
alerting-strategy
Path
engineer/devops-practices/skills/alerting-strategy/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Alerting Strategy skill do?

SLO-based alerting, threshold tuning, incident escalation, runbooks, and on-call management.

How do I install the Alerting Strategy skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Alerting Strategy popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.