How does it prevent 'alert fatigue'?

The skill enforces principles of selectivity, deduplication, and rate limiting, ensuring that operations teams only receive high-signal alerts that require action.

What severity levels are supported?

The skill defines three main levels: Critical (immediate action required), High (investigation within the hour), and Warning (monitor and plan for the next business day).

How does this skill differ from standard logging?

While logs record everything that happened for later investigation, this skill focuses on alerting—which demands immediate attention for unrecoverable errors and critical system degradations.

Does it handle frontend alerting?

Yes, it provides specific guidance for frontend applications, generally recommending reporting through services like Sentry or routing through backend APIs rather than direct browser-to-service alerts.

Can it integrate with my existing alerting tools?

Yes, it includes a lookup process to scan your project for dependencies like PagerDuty, Sentry, Opsgenie, and AWS SNS to adapt to your specific technology stack.

Standardized Alerting Practices

Name: Standardized Alerting Practices
Author: thermiteau

bythermiteau

0•

Analytics & Monitoring

Establishes robust alerting conventions for application errors to ensure critical failures reach operations teams effectively.

This skill provides a comprehensive framework for implementing error alerting within applications, distinguishing alerts from standard logs to prevent alert fatigue. It guides Claude to implement severity levels, capture essential context for incident response, and enforce centralized notification patterns while respecting project-specific requirements. By applying these standards during code creation or review, it ensures that fatal errors trigger actionable alerts rather than disappearing into log files, facilitating faster incident resolution and better system reliability.

Key Features

01Centralized notification routing and deduplication logic to prevent alert fatigue

02Severity-based classification (Critical, High, Warning) for error prioritization

03Code review patterns to detect silent failures and inconsistent alerting mechanisms

04Standardized context requirements for actionable, data-rich alerts

050 GitHub stars

06Automatic project-specific alerting implementation lookup and discovery

Use Cases

01Implementing global error handlers for new backend services and APIs

02Refactoring existing code to replace excessive logging with actionable alerts

03Standardizing alerting context across distributed microservices

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add thermiteau/maverick-private mav-bp-alerting

For use in Claude.ai and ChatGPT

Key Features

01Centralized notification routing and deduplication logic to prevent alert fatigue

02Severity-based classification (Critical, High, Warning) for error prioritization

03Code review patterns to detect silent failures and inconsistent alerting mechanisms

04Standardized context requirements for actionable, data-rich alerts

050 GitHub stars

06Automatic project-specific alerting implementation lookup and discovery

Use Cases

01Implementing global error handlers for new backend services and APIs

02Refactoring existing code to replace excessive logging with actionable alerts

03Standardizing alerting context across distributed microservices

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add thermiteau/maverick-private mav-bp-alerting

For use in Claude.ai and ChatGPT