Individual skill
alerting-context
Pull incident context from alerting platforms (PagerDuty). Use when investigating who's on-call, incident history, alert patterns, or MTTR metrics.
sre-agent/.claude/skills/alerting-context/SKILL.md
Source commit 2323af0551856ff4669b73dc36329d16aa19ed24
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 179
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-sre Repository topic
- site-reliability-engineering Repository topic
- ai-agent Repository topic
- devops Repository topic
- episodic-memory Repository topic
- incident-investigation Repository topic
- incident-response Repository topic
- knowledge-graph Repository topic
- sre-agent Repository topic
- self-hosted Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesSKILL.mdcore · 5,422 bytesscripts/__init__.pyruns · 37 bytesscripts/calculate_mttr.pyruns · 3,222 bytesscripts/get_incident.pyruns · 4,335 bytesscripts/list_incidents.pyruns · 3,868 bytesscripts/pagerduty_client.pyruns · 8,894 bytes
Read excerpt
# Alerting Context
## Authentication
**IMPORTANT**: Credentials are injected automatically by a proxy layer. Do NOT check for `PAGERDUTY_API_KEY` in environment variables - it won't be visible to you. Just run the scripts directly; authentication is handled transparently.
---
## Why Alerting Context Matters
Before diving into logs and metrics, understand:
- **Has this happened before?** Check similar past incidents
- **Who's responding?** Know who's on-call and assigned
- **What else is alerting?** Correlated alerts reveal scope