troubleshooting-notifications

Analyze Mission Control notifications to identify root causes and generate remediation steps.

Updated Nov 12, 2025
One-click install
npx skills add https://github.com/flanksource/claude-code-plugin --skill troubleshooting-notifications
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting-notifications
Source: https://github.com/flanksource/claude-code-plugin/tree/main/skills/notifications
Command: npx skills add https://github.com/flanksource/claude-code-plugin --skill troubleshooting-notifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alert fatigue and the complexity of tracing notifications back to their root cause can overwhelm teams. This Skill automates the investigation of Mission Control notifications, providing clear diagnoses and actionable remediation steps, reducing manual effort and incident resolution time.

Core Features & Use Cases

  • Notification Detail Analysis: Automatically retrieve and interpret notification titles, messages, severity, and affected resources.
  • Historical Pattern Identification: Analyze past notifications for the same resource to identify recurring issues or new incidents.
  • Intelligent Routing: Automatically invoke other specialized troubleshooting skills (e.g., config_item, health) based on the notification's resource type.
  • Actionable Remediation: Deliver clear root causes, supporting evidence, and step-by-step actions to resolve the issue and prevent recurrence.
  • Use Case: You receive an alert about an "Unhealthy Kubernetes Deployment". Use this Skill to automatically investigate the notification, trace it to the specific pod, identify a memory limit issue, and suggest a configuration change.

Quick Start

Investigate the notification with ID 'alert-123' and tell me why it triggered.

Frequently Asked Questions about troubleshooting-notifications

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

FAQPage Schema
How do I investigate why a Mission Control alert triggered?

Investigate notifications by retrieving alert details, analyzing severity and timestamps, and correlating with historical patterns to identify root causes. This Skill automatically traces notifications back to their originating resources and delivers step-by-step remediation steps.

Can I trace recurring alerts back to their root cause?

Yes. The Skill analyzes past notifications for the same resource to identify recurring issues versus new incidents, helping you spot patterns and underlying problems driving alert fatigue.

How do I get actionable remediation steps from an alert?

Provide the notification ID and the Skill retrieves the alert message, identifies the affected ConfigItem or HealthCheck resource, diagnoses the root cause, and delivers clear remediation actions plus prevention recommendations.

Does this work with Kubernetes and other resource types?

Yes. The Skill intelligently routes to resource-specific troubleshooters based on notification type, supporting Kubernetes deployments, ConfigItems, HealthChecks, and other Mission Control resources.

What information do I need to troubleshoot a notification?

Provide the notification ID. The Skill retrieves all required details—title, message, severity, affected resource, and historical context—to diagnose the issue without manual log collection.

Why does alert fatigue happen and how does this help?

Alert fatigue occurs when teams cannot quickly trace alerts to root causes, leading to missed critical issues. This Skill automates diagnosis and delivers focused remediation, reducing manual triage time and incident resolution complexity.