actionable-alerting-runbook-design
Designing effective alerts and runbooks for incident response. PROACTIVELY activate for: (1) Creating alerting rules, (2) Writing runbooks, (3) Reducing alert fatigue, (4) On-call escalation setup, (5) Incident response procedures. Triggers: "alerting", "runbook", "on-call", "pagerduty", "incident", "alert fatigue", "escalation", "playbook"
Best use case
actionable-alerting-runbook-design is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Designing effective alerts and runbooks for incident response. PROACTIVELY activate for: (1) Creating alerting rules, (2) Writing runbooks, (3) Reducing alert fatigue, (4) On-call escalation setup, (5) Incident response procedures. Triggers: "alerting", "runbook", "on-call", "pagerduty", "incident", "alert fatigue", "escalation", "playbook"
Teams using actionable-alerting-runbook-design should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/actionable-alerting-runbook-design/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How actionable-alerting-runbook-design Compares
| Feature / Agent | actionable-alerting-runbook-design | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Designing effective alerts and runbooks for incident response. PROACTIVELY activate for: (1) Creating alerting rules, (2) Writing runbooks, (3) Reducing alert fatigue, (4) On-call escalation setup, (5) Incident response procedures. Triggers: "alerting", "runbook", "on-call", "pagerduty", "incident", "alert fatigue", "escalation", "playbook"
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Actionable Alerting and Runbook Design This skill provides expertise in designing alerts and runbooks for effective incident response. ## Overview Good alerting enables quick incident detection and resolution. Bad alerting causes fatigue and missed issues. ## Alerting Principles ### What Makes an Alert Actionable? 1. **Specific**: Clear about what's wrong 2. **Contextual**: Includes relevant information 3. **Timely**: Fires before users notice 4. **Actionable**: Recipient can do something about it 5. **Linked**: Points to runbook or dashboard ### Alert Anti-Patterns - **Flapping alerts**: Constantly firing and resolving - **Too sensitive**: Alerts on normal variance - **No runbook**: Alert with no remediation guidance - **Wrong audience**: Alerting people who can't help ## Runbook Structure ```markdown # Alert: High API Error Rate ## Summary API error rate exceeds 5% for 5 minutes ## Impact Users experiencing failed requests ## Diagnosis Steps 1. Check error logs: [link] 2. Check recent deployments: [link] 3. Check database health: [link] ## Remediation Steps 1. If recent deployment, rollback: `kubectl rollout undo...` 2. If database issue, scale: `gcloud sql instances patch...` 3. If unknown, escalate to: @team-leads ## Escalation - L1: On-call engineer - L2: Team lead (if not resolved in 15min) - L3: VP Engineering (if customer impact > 30min) ``` ## Best Practices 1. Alert on symptoms, not causes 2. Use multi-window alerting to reduce noise 3. Include dashboards and runbook links in alerts 4. Review and prune alerts quarterly 5. Track alert-to-incident ratio [Content to be expanded based on plugin_spec_agentient-observability.md specifications]
Related Skills
Advanced Modular Library Design
Design modular libraries with clear package boundaries, feature-first organization, and clean API surfaces. Use when structuring monorepos, defining module boundaries, or designing library APIs.
admin-design
Minimal, high-clarity admin UI design for this repo. Use when redesigning /admin pages (translation manager, dashboards, tables, forms), defining admin design tokens, or improving admin UX/keyboard workflows without changing core functionality.
adhd-design-expert
Designs digital experiences for ADHD brains using neuroscience research and UX principles. Expert in reducing cognitive load, time blindness solutions, dopamine-driven engagement, and compassionate design patterns. Activate on 'ADHD design', 'cognitive load', 'accessibility', 'neurodivergent UX', 'time blindness', 'dopamine-driven', 'executive function'. NOT for general accessibility (WCAG only), neurotypical UX design, or simple UI styling without ADHD context.
actionable-review-format-standards
Standardized output format for code reviews with severity labels, file:line references, and fix code snippets. Use when generating review reports that need consistent, actionable feedback structure.
action-mapping-designer
This skill should be used when ensuring training focuses on performance outcomes and business impact. Use this skill to identify essential content, design performance-focused activities, create job aids, and eliminate unnecessary training.
accessibility-design-checklist
Эксперт по accessibility дизайну. Используй для WCAG, a11y чеклистов и inclusive design.
accessibility-design-checker
Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.
---name: aav-vector-design-agent
description: AI-powered adeno-associated virus (AAV) vector design for gene therapy including capsid engineering, promoter selection, and tropism optimization.
Swift iOS Design Best Practices
Comprehensive guide to UI/UX design principles, architectural patterns, and animation techniques for building high-quality iOS apps with Swift.
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
design
Create and manage project-specific design systems for SaaS applications. Use when starting a new app (CREATE mode), updating an existing design system (MODIFY mode), or building features that need to follow established patterns (WORK WITHIN mode). Outputs to instructions/design-system.md as the single source of truth for all UX/UI decisions.