Alert Management
SkillMonitoring & opsThis skill gives your AI the ability to set up and manage alerting so the right people hear about problems quickly. Once added, your AI can create alerts in PagerDuty, write escalation policies, and coordinate incident response when something goes wrong.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding the skill, describe what should trigger alerts and who should respond, and your AI will help you set it up and manage on-call going forward.
Then ask your AI: use the Alert Management skill
What your AI can do with it
- Set up alerting systems in PagerDuty
- Create escalation policies so alerts reach the right people
- Manage on-call schedules
- Coordinate incident response when alerts fire
What this skill tells your AI
The instructions your AI receives, as published by aj-geddes/useful-ai-prompts in skills/alert-management/SKILL.md and read by ahel’s review.
Table of Contents
- Overview
- When to Use
- Quick Start
- Reference Guides
- Best Practices
Overview
Design and implement sophisticated alert management systems with PagerDuty integration, escalation policies, alert routing, and incident coordination.
When to Use
- Setting up alert routing
- Managing on-call schedules
- Coordinating incident response
- Creating escalation policies
- Integrating alerting systems
Quick Start
Minimal working example:
// pagerduty-client.js
const axios = require("axios");
class PagerDutyClient {
constructor(apiToken) {
this.apiToken = apiToken;
this.baseUrl = "https://api.pagerduty.com";
this.eventUrl = "https://events.pagerduty.com/v2/enqueue";
this.client = axios.create({
baseURL: this.baseUrl,
headers: {
Authorization: `Token token=${apiToken}`,
Accept: "application/vnd.pagerduty+json;version=2",
},
});
}
async triggerEvent(config) {
const event = {
routing_key: config.routingKey,
event_action: config.eventAction || "trigger",
dedup_key: config.dedupKey || `event-${Date.now()}`,
payload: {
summary: config.summary,
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| PagerDuty Client Integration | PagerDuty Client Integration |
| Alertmanager Configuration | Alertmanager Configuration |
| Alert Handler Middleware | Alert Handler Middleware |
| Alert Routing Engine | Alert Routing Engine |
| Docker Compose Alert Stack | Docker Compose Alert Stack |
Best Practices
✅ DO
- Set appropriate thresholds
- Implement alert deduplication
- Use clear alert names
- Include runbook links
- Configure escalation properly
- Test alert rules
- Monitor alert quality
- Set repeat intervals
- Track alert metrics
- Document alert meanings
❌ DON'T
- Alert on every anomaly
- Ignore alert fatigue
- Set thresholds arbitrarily
- Skip runbooks
- Alert without action
- Disable alerts in production
- Use vague alert names
- Forget escalation policies
- Re-alert too frequently
Signals
- GitHub stars
- 336
- Forks
- 55
- Last commit
- Mar 2026
Advanced
- Catalog kind
- skill
- Gateway key
alert-management- Source
- github.com/aj-geddes/useful-ai-prompts