Creating Alerting RulesSAFE

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: creating-alerting-rules
description: 'Execute this skill enables AI assistant to create intelligent alerting
  rules for proactive performance monitoring. it is triggered when the user requests
  to "create alerts", "define monitoring rules", or "set up alerting". the skill helps
  define thresholds, rou... Use when generating or creating new content. Trigger with
  phrases like ''generate'', ''create'', or ''scaffold''.

  '
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(cmd:*)
version: 1.21.0
author: Jeremy Longshore <[email protected]>
license: MIT
tags:
- performance
- monitoring
- alerting-rules
compatibility: Designed for Claude Code
---
# Alerting Rule Creator

Create production-ready alerting rules for Prometheus, Grafana, and PagerDuty with intelligent thresholds, routing policies, and escalation procedures.

## Overview

This skill automates the creation of comprehensive alerting rules, reducing the manual effort required for performance monitoring. It guides you through defining alert categories, setting intelligent thresholds, and configuring routing and escalation policies. The skill also helps generate runbooks and establish alert testing procedures.

## How It Works

1. **Identify Alert Category**: Determines the type of alert to create (e.g., latency, error rate, resource utilization).
2. **Define Thresholds**: Sets appropriate thresholds to avoid alert fatigue and ensure timely notification of performance issues.
3. **Configure Routing and Escalation**: Establishes routing policies to direct alerts to the appropriate teams and escalation policies for timely response.
4. **Generate Runbook**: Creates a basic runbook with steps to diagnose and resolve the alerted issue.

## When to Use This Skill

This skill activates when you need to:

- Implement performance monitoring for a new service.
- Refine existing alerting rules to reduce false positives.
- Create alerts for specific performance metrics, such as latency or error rate.

## Examples

### Example 1: Setting up Latency Alerts

User request: "create latency alerts for the payment service"

The skill will:

1. Prompt for latency thresholds (e.g., warning and critical).
2. Configure alerts to trigger when latency exceeds defined thresholds.

### Example 2: Creating Error Rate Alerts

User request: "set up alerting for error rate increases in the API gateway"

The skill will:

1. Request the baseline error rate and acceptable deviation.
2. Configure alerts to trigger when the error rate exceeds the defined deviation from the baseline.

## Best Practices

- **Threshold Selection**: Use historical data and statistical analysis to determine appropriate thresholds that minimize false positives and negatives.
- **Alert Routing**: Route alerts to the appropriate teams or individuals based on the alert category and severity.
- **Runbook Creation**: Generate or link to detailed runbooks that provide clear instructions for diagnosing and resolving the alerted issue.

## Integration

This skill can be integrated with other Claude Code plugins to automate incident response workflows. For example, it can trigger automated remediation actions or create tickets in an issue tracking system.

## Prerequisites

- Appropriate file access permissions
- Required dependencies installed

## Instructions

1. Invoke this skill when the trigger conditions are met
2. Provide necessary context and parameters
3. Review the generated output
4. Apply modifications as needed

## Output

The skill produces structured output relevant to the task.

## Error Handling

- Invalid input: Prompts for correction
- Missing dependencies: Lists required components
- Permission errors: Suggests remediation steps

## Resources

- Project documentation
- Related skills and commands

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

declared (1 observation(s))

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.