@tank/kubectl-cheatsheet

Generate kubectl command references for Kubernetes operations.

1|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/tankpkg/packages --skill tank-kubectl-cheatsheet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @tank/kubectl-cheatsheet
Source: https://github.com/tankpkg/packages/tree/main/skills/kubectl-cheatsheet
Command: npx skills add https://github.com/tankpkg/packages --skill tank-kubectl-cheatsheet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps Kubernetes operators quickly find the right kubectl command for inspecting clusters, debugging workloads, and safely making common operational changes without hunting through documentation.

Core Features & Use Cases

  • Fast command lookup: Covers the most common kubectl actions for pods, deployments, services, nodes, namespaces, configmaps, and secrets.
  • Operational debugging: Helps with high-frequency troubleshooting tasks such as checking status, reading logs, describing resources, and investigating failed rollouts.
  • Safe cluster changes: Includes practical guidance for apply, delete, scale, rollout, patch, label, and annotation workflows with namespace awareness and output shaping.
  • Real-world example: When a pod is crashing, the Skill points you from get to describe to logs and then to the right recovery or rollout command.

Quick Start

Use this skill to find the safest kubectl command for inspecting a failing pod, checking rollout status, or targeting the correct namespace in your current Kubernetes cluster.

Frequently Asked Questions about @tank/kubectl-cheatsheet

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

FAQPage Schema
How do I find the right kubectl command to debug a crashing pod?

To debug a crashing pod, you need kubectl commands that transition from inspecting status to reading logs and describing resources. This reference provides a progression flow from get to describe to logs, and then to the appropriate recovery or rollout command for safe workload inspection.

What is the best way to check a Kubernetes deployment rollout status?

Checking a Kubernetes deployment rollout status requires using kubectl rollout commands with proper namespace targeting. This reference supplies operational commands for investigating failed rollouts, checking status, and safely managing deployment updates within your cluster.

Can I use kubectl to safely scale and patch resources in a specific namespace?

Yes, you can use kubectl to safely scale and patch resources by applying namespace-aware commands. This reference includes practical guidance for apply, delete, scale, patch, label, and annotation workflows with namespace awareness and output shaping for safe cluster changes.

How do I format kubectl output and use selectors to filter Kubernetes resources?

Formatting kubectl output and filtering Kubernetes resources requires using specific output formatting flags and label selectors. This reference covers output shaping and selector usage to help you target the correct resources and extract the exact data needed for operations.

What kubectl commands do I need for inspecting configmaps and secrets?

Inspecting configmaps and secrets requires specific kubectl commands tailored for these sensitive resources. This reference covers the most common actions for configmaps and secrets, ensuring safe inspection and mutation practices within your Kubernetes cluster.

Does this kubectl reference cover port-forward and exec operations for troubleshooting?

Yes, this kubectl reference covers port-forward and exec operations specifically for high-frequency troubleshooting tasks. It provides the commands needed to access running pods directly, facilitating operational debugging and direct workload investigation.