skills.rest
eveld
eveldCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

k8s-awareness

Debug Kubernetes workloads using structured locator, analyzer, and pattern-finder workflows.

10|2|Updated Dec 23, 2025
Search Tags:#debugging#kubernetes#k8s#analyzer#locator#pattern-finder
One-click install
npx skills add https://github.com/eveld/claude --skill k8s-awareness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: k8s-awareness
Source: https://github.com/eveld/claude/tree/main/skills/k8s-awareness
Command: npx skills add https://github.com/eveld/claude --skill k8s-awareness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kubernetes debugging often relies on ad-hoc kubectl commands that lack consistency and documentation. This skill provides a structured set of Kubernetes-specific debugging workflows to replace raw kubectl.

Core Features & Use Cases

  • Guided workflows for resource locator, health analysis, and pattern detection across namespaces.
  • Replaces ad-hoc commands with well-documented steps using dedicated K8s tools like k8s-locator, k8s-analyzer, k8s-pattern-finder, and k8s-debug.
  • Use cases include diagnosing pod failures, cross-namespace investigations, and cluster-wide issue spotting with traceable results.

Quick Start

Request Kubernetes debugging guidance by applying the k8s-awareness skill to inspect a pod in the target namespace.

Frequently Asked Questions about k8s-awareness

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

FAQPage Schema
How do I debug Kubernetes pod failures without relying on raw kubectl commands?▼

To debug Kubernetes pod failures without raw kubectl commands, this Skill applies structured workflows using specialized tools like k8s-locator, k8s-analyzer, and k8s-pattern-finder for traceable, consistent results.

What is the best way to investigate issues across multiple Kubernetes namespaces?▼

The best way to investigate issues across multiple Kubernetes namespaces is using guided workflows that enforce pre-flight context checks and guardrails for resource access, ensuring safe cross-namespace analysis.

How does the k8s-debug integration work for ephemeral debugging containers?▼

The k8s-debug integration works by attaching ephemeral debugging containers to target workloads, enabling safe, temporary investigation without permanently altering the pod's original specification.

Can I use this approach to detect cluster-wide patterns in my Kubernetes environment?▼

Yes, you can detect cluster-wide patterns in your Kubernetes environment by applying the pattern-finder workflow, which spots cluster-wide issues and traces them back to their root causes.

What is the difference between ad-hoc kubectl and structured Kubernetes debugging workflows?▼

Structured Kubernetes debugging workflows replace ad-hoc kubectl by providing well-documented steps, dedicated K8s tools, and predictable locator, analyzer, and pattern-finder phases for consistent issue diagnosis.

Do I need to set up pre-flight context checks before analyzing Kubernetes workloads?▼

Yes, pre-flight context checks are enforced automatically before analyzing Kubernetes workloads, ensuring the correct target context and resource access guardrails are established prior to debugging.

Related Skills

Explore More Software Engineering Skills→
Matchpoint-AIMatchpoint-AI

rackspace-spot-access

Retrieve a Rackspace Spot kubeconfig and debug ARC runners with spotctl.

Official
Advanced
Sir-chawakornSir-chawakorn
9

k8s-debug-workload

Diagnose Kubernetes workload failures by analyzing pod status, events, logs, and node constraints.

Community
Advanced
ChanghwanKChanghwanK

devops:storage-ops

Diagnose Rook-Ceph cluster health and PVC issues in the infra-k8s-idc cluster.

Community
Advanced
jimwellerjimweller

k8s-steampipe

Query Kubernetes cluster resources using Steampipe SQL.

Community
Intermediate