cluster-events

Analyze Kubernetes cluster-wide Warning events to diagnose issues and identify patterns.

225|28|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/scitix/siclaw --skill cluster-events
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cluster-events
Source: https://github.com/scitix/siclaw/tree/main/skills/core/cluster-events
Command: npx skills add https://github.com/scitix/siclaw --skill cluster-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps SREs and DevOps engineers quickly identify and understand issues occurring across a Kubernetes cluster by analyzing event logs.

Core Features & Use Cases

  • Event Aggregation: Collects and filters Warning events cluster-wide.
  • Pattern Detection: Identifies high-frequency events indicating recurring problems.
  • Resource Correlation: Links related events to a specific resource for deeper analysis.
  • Root Cause Guidance: Provides actionable next steps and suggests relevant diagnostic skills based on event types.
  • Use Case: When pods are failing to start, this skill can analyze FailedScheduling or ImagePullBackOff events to pinpoint the cause and recommend the pod-pending-debug or image-pull-debug skill.

Quick Start

Analyze all warning events in the Kubernetes cluster to identify potential issues.

Frequently Asked Questions about cluster-events

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

FAQPage Schema
How do I diagnose Kubernetes cluster issues from warning events?

Diagnose Kubernetes cluster issues by analyzing cluster-wide events, which aggregates Warning events, detects high-frequency occurrences, and correlates them by resource to pinpoint root causes.

Why are my Kubernetes pods failing to schedule or pulling images?

Pods failing to schedule or pull images trigger FailedScheduling, BackOff, and ErrImagePull events. Analyzing these cluster events identifies the specific failure pattern and recommends the appropriate diagnostic skill.

How do I find the root cause of OOMKilling or NodeNotReady events in Kubernetes?

Find the root cause of OOMKilling or NodeNotReady events by correlating related events to the specific affected resource, providing actionable next steps and suggesting targeted diagnostic skills.

Can I detect recurring high-frequency problems across a Kubernetes cluster?

You can detect recurring high-frequency problems across a Kubernetes cluster by aggregating and filtering cluster-wide Warning events to identify patterns indicating repeated failures.

What is the best way to troubleshoot Kubernetes pods stuck in pending states?

The best way to troubleshoot pending pods is analyzing FailedScheduling cluster events to pinpoint the cause and recommend specific diagnostic skills like pod-pending-debug for deeper analysis.

Does analyzing cluster events work for diagnosing ErrImagePull failures?

Analyzing cluster events works for diagnosing ErrImagePull failures by matching the event pattern and recommending specific diagnostic skills like image-pull-debug for targeted troubleshooting.