alerting-engineering

Design alerting that gets paged for the right reasons.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/0xzahed-alerting-engineering

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Design alerting that gets paged for the right reasons. Use when defining alert rules and policies.

Use cases: design

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/alerting-engineering

What's inside

Skill name: alerting-engineering
Description: Design alerting that gets paged for the right reasons. Use when defining alert rules and policies.
License: MIT
Metadata: tags: alerting, engineering
Instructions: 34 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Alerting Engineering

## Use this skill when
- Turning SLOs and metrics into alerts
- Setting severity, escalation, and routing
- Reducing alert noise

## Do not use this skill when
- Building dashboards
- Debugging a system (incident playbook)

## Instructions
1. Alert on user impact symptoms and SLO burn, not every dip.
2. Set paging thresholds so real incidents page; everything else goes to an issue.
3. Include runbook links, severity, and owner in every alert.
4. Use alerting on rate/trend, not raw thresholds alone.
5. Keep a max alerts-per-person budget; retire noise.
6. Escalate on silence or repetition.
7. Post-incident, tune alerts as follow-up.

## Checklist
- Every alert links a runbook
- No on-call fatigue from noise
- SLO burn alerts present

## Output Format
- Alert | condition | severity | owner | runbook | frequency

## Common Mistakes
- Paging from a dashboard graph
- Threshold alerts that always fire
- No retirement of stale alerts

From 0xzahed/antigravity-skills, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/0xzahed/antigravity-skills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from 0xzahed

Cite this page

alerting-engineering skill. Agent Mart. https://agentmart.dev/skills/0xzahed-alerting-engineering (last updated 2026-10-24)