skills.rest
cornmanwtf
cornmanwtfCOMMUNITY
Explore all skills by this author →
GitHub

alerting-and-monitoring

Define alerts, escalation policies, and incident response procedures for systems.

Updated Jan 16, 2026
Search Tags:#devops#monitoring#incident response#alerting#escalation#system health
One-click install
npx skills add https://github.com/cornmanwtf/ABANG-COLEK --skill alerting-and-monitoring
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alerting-and-monitoring
Source: https://github.com/cornmanwtf/ABANG-COLEK/tree/main/skills/devops-infra/alerting-and-monitoring
Command: npx skills add https://github.com/cornmanwtf/ABANG-COLEK --skill alerting-and-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to defining and implementing alerting, escalation policies, and incident response procedures for systems and applications.

Core Features & Use Cases

  • Alert Definition: Specifies conditions under which alerts are triggered.
  • Escalation Policies: Outlines how alerts are routed and escalated to the appropriate teams.
  • Incident Response: Details the steps to take when an incident occurs.
  • Use Case: Setting up alerts for high CPU usage on a production server, defining an escalation path to the on-call engineer, and outlining the steps for diagnosing and resolving the issue.

Quick Start

Define alerts and escalation policies for the production web servers.

Frequently Asked Questions about alerting-and-monitoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define alerting and escalation policies for production servers?▼

To define alerting and escalation policies, you specify trigger conditions for alerts and map out routing paths to the appropriate on-call teams. This structured approach ensures system health issues are escalated correctly for incident response.

What steps should I include in an incident response procedure for high CPU usage?▼

Incident response procedures for high CPU usage should detail the diagnostic steps to identify the bottleneck and the specific resolution actions required. The process integrates with CLI and SDK tooling to execute these remediation steps effectively.

Can I use this approach to monitor non-functional requirements like security and compliance?▼

Yes, you can monitor non-functional requirements like security, performance, and compliance. You define alerts triggered by specific system health thresholds to maintain application standards and meet compliance requirements.

Do I need environment credentials to set up system health monitoring and alerting?▼

Yes, environment credentials are required to set up system health alerting. The framework integrates with CLI and SDK tooling for target stacks, requiring authenticated access to manage alerts and execute incident response procedures.

Related Skills

Explore More Software Engineering Skills→
cornmanwtfcornmanwtf

secret-injection

Inject secrets from platform providers and environment variables into application deployments.

Community
Advanced
PM-ShawnPM-Shawn
269

alert-sop

Analyze system alerts and generate incident reports from SOPs.

Community
Advanced
huivrotikihuivrotiki

pagerduty-automation

Automate PagerDuty incident lifecycle and on-call workflows via Rube MCP.

Community
Advanced
alexmaruccialexmarucci

dd-monitors

Automate Datadog monitor creation, updating, and alerting configuration via pup CLI.

Community
Advanced