k8s-work

Diagnoses and resolves issues in local Kubernetes development clusters.

15|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/selhorys/dataspoke-baseline --skill k8s-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-work
Source: https://github.com/selhorys/dataspoke-baseline/tree/main/.claude/skills/k8s-work
Command: npx skills add https://github.com/selhorys/dataspoke-baseline --skill k8s-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and troubleshoot a local Kubernetes development cluster by providing health checks, continuous monitoring, and essential kubectl/helm operations.

Core Features & Use Cases

  • Health checks for nodes, pods, namespaces, and cluster components to quickly surface issues.
  • Continuous monitoring guidance and diagnostic workflows to keep the local cluster healthy.
  • Safe, repeatable kubectl/helm operation patterns and troubleshooting steps that minimize risk in a local dev environment.

Quick Start

Run the k8s-work skill to perform an initial health snapshot of your local Kubernetes cluster and generate a concise troubleshooting guide.

Frequently Asked Questions about k8s-work

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

FAQPage Schema
How do I troubleshoot a local Kubernetes cluster when pods are failing?

Troubleshoot a local Kubernetes cluster by running an initial health snapshot to check nodes, pods, namespaces, and components. This surfaces issues quickly and generates a concise diagnostic workflow guide for safe remediation.

What is the best way to run a Kubernetes health check in Minikube or Docker Desktop?

The best way to run a Kubernetes health check in Minikube or Docker Desktop is to execute automated diagnostic workflows that provide real-time status reporting on nodes, pods, and essential tools like kubectl and helm.

Why does my local Kubernetes development environment have unresolved deployment issues?

Your local Kubernetes development environment may have unresolved issues because underlying cluster components or essential tools like helm are unhealthy. Running continuous monitoring and health checks helps identify these specific problems.

Can I use kubectl and helm operation patterns without accidentally deleting resources?

Yes, you can use kubectl and helm operation patterns safely without deleting resources. The troubleshooting steps provide safe, repeatable recommendations designed specifically to minimize risk in a local dev environment.

What should I do when continuous monitoring shows node failures in my local cluster?

When continuous monitoring shows node failures in your local cluster, follow the generated troubleshooting guidance to safely remediate the issue. The diagnostic workflows provide safe recommendations without deleting resources.