Agent skill · magnus919
kubernetes
Operate, troubleshoot, secure, upgrade, and automate Kubernetes clusters and workloads safely across upstream Kubernetes, k3s, RKE2, MicroK8s, k0s, Talos, OpenShift/OKD, kind, Minikube, Rancher-managed clusters, EKS, AKS, and GKE. Use when a task involves kubectl, Kubernetes APIs, Pods, Deployments, StatefulSets, Services, Ingress or Gateway API, CRDs, RBAC, NetworkPolicy, storage, scheduling, autoscaling, cluster lifecycle, or the bundled agent-first k8s-cli.
What it needs
About 3k tokens when loaded.
What this skill does
Kubernetes Use this skill as a decision and routing layer. Do not treat it as a static kubectl cheat sheet. Operating contract 1. Identify the target: distribution, provider, cluster version, client version, context, namespace, access mode, and whether the cluster is production. 2. Discover before assuming: query served API resources, API versions, CRDs, system workloads, nodes, and distribution markers. 3. Separate portable Kubernetes behavior from distribution/provider overlays. Load the matching reference before using lifecycle, networking, identity, storage, or upgrade instructions. 4. For mutations, preview first (k8s-cli ... --dry-run or kubectl diff / server dry-run), state scope, require explicit confirmation for destructive actions, then verify conditions, events, rollout, and the external boundary. 5. Prefer stable APIs and server-side validation. Treat beta/alpha APIs, feature gates, provider defaults, and version numbers as time-sensitive. 6. Keep evidence bounded and structured. Never dump kubeconfigs, Secret values, tokens, or unbounded logs into chat. Choose the operating path Situation First move Do not do --- --- --- Live cluster operation Run doctor, context, and discover; record context, namespace, distribution, and versions Do not infer cluster state from configuration or a prior command No cluster access Produce a bounded plan and name the missing prerequisite Do not claim a diagnosis, success, or invented command output Any mutation Render, diff/server-dry-run, state scope, obtain the required confirmation, then mutate and verify the relevant boundary Do not treat command exit 0 as operational success Provider or distribution present Load the matching overlay before applying portable guidance Do not apply upstream instructions unchanged First-response discovery If the wrapper is unavailable, use the equivalent native commands from references/cli-reference.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/kubernetes