How do I install the Kubernetes Principal Engineer skill?

Run npx skillmds@latest add modra40/kubernetes-principal-engineer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubernetes Principal Engineer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubernetes Principal Engineer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubernetes Principal Engineer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubernetes Principal Engineer?

modra40 (@modra40) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubernetes Principal Engineer by modra40

Name: Kubernetes Principal Engineer
Author: modra40

Kubernetes Principal Engineer

Principal/Senior-level Kubernetes playbook for workload design, cluster operations, networking, security, observability, deployment safety, and platform reliability. Use when: designing manifests and controllers, operating clusters, debugging production incidents, reviewing platform architecture, or shipping workloads safely on Kubernetes.

modra40 0c90060 16 files · 9.7 KB Updated Sep 17, 2026

File contents

Kubernetes Mastery (Senior → Principal)

Operate

Start from workload SLOs, failure model, team ownership, and platform constraints.
Treat Kubernetes as a distributed control plane, not merely a YAML bucket.
Prefer operational clarity over abstract platform cleverness.
Design for rollout safety, debuggability, and failure containment.

Default Standards

Requests/limits should be intentional.
Health probes must reflect real readiness.
Rollouts need safe defaults and rollback posture.
RBAC and network policy should be least-privilege by default.
Observability and runbooks are part of workload design.

References

Workload design: references/workload-design.md
Pods, deployments, and rollout safety: references/pods-deployments-and-rollouts.md
Services and ingress: references/services-and-ingress.md
Networking and network policy: references/networking-and-network-policy.md
Storage and stateful workloads: references/storage-and-stateful-workloads.md
Security and RBAC: references/security-and-rbac.md
Resource management: references/resource-management.md
Scheduling and autoscaling: references/scheduling-and-autoscaling.md
Observability: references/observability.md
Debugging and troubleshooting: references/debugging-and-troubleshooting.md
Multi-tenant clusters: references/multi-tenant-clusters.md
Platform operations: references/platform-operations.md
Disaster recovery: references/disaster-recovery.md
GitOps and delivery workflows: references/gitops-and-delivery-workflows.md
Incident runbooks: references/incident-runbooks.md

---name: kubernetes-principal-engineerdescription: Principal/Senior-level Kubernetes playbook for workload design, cluster operations, networking, security, observability, deployment safety, and platform reliability. Use when: designing manifests and controllers, operating clusters, debugging production incidents, reviewing platform architecture, or shipping workloads safely on Kubernetes.---# Kubernetes Mastery (Senior → Principal)## Operate- Start from workload SLOs, failure model, team ownership, and platform constraints.- Treat Kubernetes as a distributed control plane, not merely a YAML bucket.- Prefer operational clarity over abstract platform cleverness.- Design for rollout safety, debuggability, and failure containment.## Default Standards- Requests/limits should be intentional.- Health probes must reflect real readiness.- Rollouts need safe defaults and rollback posture.- RBAC and network policy should be least-privilege by default.- Observability and runbooks are part of workload design.## References- Workload design: [references/workload-design.md](references/workload-design.md)- Pods, deployments, and rollout safety: [references/pods-deployments-and-rollouts.md](references/pods-deployments-and-rollouts.md)- Services and ingress: [references/services-and-ingress.md](references/services-and-ingress.md)- Networking and network policy: [references/networking-and-network-policy.md](references/networking-and-network-policy.md)- Storage and stateful workloads: [references/storage-and-stateful-workloads.md](references/storage-and-stateful-workloads.md)- Security and RBAC: [references/security-and-rbac.md](references/security-and-rbac.md)- Resource management: [references/resource-management.md](references/resource-management.md)- Scheduling and autoscaling: [references/scheduling-and-autoscaling.md](references/scheduling-and-autoscaling.md)- Observability: [references/observability.md](references/observability.md)- Debugging and troubleshooting: [references/debugging-and-troubleshooting.md](references/debugging-and-troubleshooting.md)- Multi-tenant clusters: [references/multi-tenant-clusters.md](references/multi-tenant-clusters.md)- Platform operations: [references/platform-operations.md](references/platform-operations.md)- Disaster recovery: [references/disaster-recovery.md](references/disaster-recovery.md)- GitOps and delivery workflows: [references/gitops-and-delivery-workflows.md](references/gitops-and-delivery-workflows.md)- Incident runbooks: [references/incident-runbooks.md](references/incident-runbooks.md)

Frequently asked questions