@tank/kubernetes-mastery

Name: @tank/kubernetes-mastery
Availability: InStock
Author: tankpkg

Diagnose Kubernetes cluster operations and deployment problems with kubectl-oriented diagnostics.

1|1|Updated Feb 20, 2026

Search Tags:#rbac #kubernetes #helm #gitops #kubectl #k8s #autoscaling

Ready to run

npx skills add https://github.com/tankpkg/packages --skill tank-kubernetes-mastery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: @tank/kubernetes-mastery
Source: https://github.com/tankpkg/packages/tree/main/skills/kubernetes-mastery
Command: npx skills add https://github.com/tankpkg/packages --skill tank-kubernetes-mastery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design, operate, and troubleshoot Kubernetes systems without guessing, reducing downtime and avoiding risky cluster changes.

Core Features & Use Cases

Workload management: Choose and configure Deployments, StatefulSets, DaemonSets, Jobs, and CronJobs for the right runtime behavior.
Networking and delivery: Set up Services, Ingress, DNS, Helm, Kustomize, and GitOps workflows for reliable application release and exposure.
Security and operations: Apply RBAC, Pod Security Standards, storage primitives, autoscaling, probes, observability, and debugging patterns for production readiness.
Use case: Turn a failing rollout, CrashLoopBackOff, pending pod, or service exposure issue into a clear diagnosis and safe remediation plan.

Quick Start

Ask this Skill to review your Kubernetes manifest or cluster symptom and return the safest production-grade fix with the most likely root cause.

Frequently Asked Questions about @tank/kubernetes-mastery

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

FAQPage Schema

How do I diagnose a CrashLoopBackOff or pending pod issue in Kubernetes?▼

Diagnose Kubernetes pod failures like CrashLoopBackOff or pending states by applying kubectl-oriented diagnostics to identify root causes and generate safe remediation plans. This approach uses YAML-first reasoning to evaluate workloads and configuration without risky cluster changes.

What is the best way to configure Kubernetes autoscaling and probes for production readiness?▼

Configure Kubernetes autoscaling and probes by applying controller-aware recommendations and safe rollout practices. This ensures workloads scale correctly and pass health checks, maintaining production readiness across single-cluster and multi-cluster environments.

How do I set up RBAC and Pod Security Standards for a k8s cluster?▼

Set up Kubernetes RBAC and Pod Security Standards by applying YAML-first reasoning to define role bindings and security policies. This secures cluster operations and workloads by ensuring safe configuration practices across deployments.

Can I use Helm and GitOps workflows for reliable Kubernetes application release?▼

Yes, you can use Helm and GitOps workflows to manage Kubernetes application releases. This networking and delivery approach ensures reliable application exposure and release by integrating Kustomize and DNS configurations across your clusters.

Does this approach work for multi-cluster Kubernetes environments and observability?▼

Yes, this approach works for multi-cluster Kubernetes environments and observability. It diagnoses cluster operations and deployment problems across single-cluster and multi-cluster setups, applying debugging patterns for comprehensive production troubleshooting.

Why do my Kubernetes deployments fail during rollout and how do I fix them safely?▼

Kubernetes deployments fail during rollout due to misconfigured controllers, probes, or RBAC settings. Fix them safely by applying controller-aware recommendations and safe rollout practices to turn failing rollouts into clear diagnoses and remediation plans.