kubernetes-skill

Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and platform-specific Kubernetes work for EKS, GKE, AKS, OpenShift, GitOps controllers, or observability stacks.

Best for production deploymentsWorks with GitHubLow risk

#kubernetes #security #failure-mode #manifest-review #helm #kustomize #eks #gke #aks

⌘source

author: @LukasNiessen
repo: LukasNiessen/kubernetes-skill
language: unknown

✦overview.md

Key Features

·Capture cluster context before writing manifests
·Diagnose six failure modes
·Fix insecurity, starvation, exposure, privilege, fragility, drift
·Works with Helm, Kustomize, raw YAML, operators
·Covers EKS, GKE, AKS, OpenShift, k3s

Use Cases

→Reviewing a Helm chart for production readiness
→Migrating workloads from on-prem to EKS
→Auditing existing manifests for privilege sprawl
→Setting up resource requests and limits for a new service
→Enforcing Pod Security Admission policies

Best for

✓production deployments
✓platform teams
✓security reviews

Not ideal for

!one-off scripts
!non-containerized apps
!local Minikube testing

FAQs

SKILL.md

name

kubernetes-skill

description

KubeShark: Failure-Mode Workflow for Kubernetes

Run this workflow top to bottom.

1) Capture execution context

Record before writing manifests:

cluster version (e.g. 1.30, 1.31) and distribution (EKS, GKE, AKS, k3s, vanilla)
target namespace and environment criticality (dev/staging/prod)
workload type (Deployment, StatefulSet, Job, CronJob, DaemonSet)
deployment method (raw YAML, Helm, Kustomize, operator-managed)
policy enforcement (Pod Security Admission level, Kyverno, OPA/Gatekeeper)
cloud provider and CNI (affects networking, storage classes, load balancers)
platform controllers/add-ons (GitOps, observability, ingress, service mesh, autoscaling)

If unknown, state assumptions explicitly.

2) Diagnose likely failure mode(s)

Select one or more based on user intent and risk:

insecure workload defaults: missing security contexts, PSS violations, host access
resource starvation: missing requests/limits, no PDB, scheduling chaos
network exposure: flat networking, missing policies, wrong Service types, DNS issues
privilege sprawl: overly permissive RBAC, leaked secrets, excess ServiceAccount rights

...

$install

1-click copy

npx skills add LukasNiessen/kubernetes-skill --skill kubernetes-skill

Safety assessment

★

Clarity score

How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.

4/ 5

very good

Clear and well structured, with only minor parts that might need a second read.

◎

Actionability score

How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.

4/ 5

high

Mostly actionable with clear steps; only a few small gaps remain.

~community cookbook

May 8, 2026

◧ Compare

kubernetes-skill

Best for production deploymentsWorks with GitHubLow risk

KubeShark: Failure-Mode Workflow for Kubernetes

Run this workflow top to bottom.

1) Capture execution context

Record before writing manifests:

cluster version (e.g. 1.30, 1.31) and distribution (EKS, GKE, AKS, k3s, vanilla)

target namespace and environment criticality (dev/staging/prod)

workload type (Deployment, StatefulSet, Job, CronJob, DaemonSet)

deployment method (raw YAML, Helm, Kustomize, operator-managed)

policy enforcement (Pod Security Admission level, Kyverno, OPA/Gatekeeper)

cloud provider and CNI (affects networking, storage classes, load balancers)

platform controllers/add-ons (GitOps, observability, ingress, service mesh, autoscaling)

If unknown, state assumptions explicitly.

2) Diagnose likely failure mode(s)

Select one or more based on user intent and risk:

insecure workload defaults: missing security contexts, PSS violations, host access

resource starvation: missing requests/limits, no PDB, scheduling chaos

network exposure: flat networking, missing policies, wrong Service types, DNS issues

privilege sprawl: overly permissive RBAC, leaked secrets, excess ServiceAccount rights

kubernetes-skill

Key Features

Use Cases

Best for

Not ideal for

FAQs

Which Kubernetes distributions are supported?

Does this work for Helm charts?

What failure modes does it check?

Is cluster access required?

KubeShark: Failure-Mode Workflow for Kubernetes

1) Capture execution context

2) Diagnose likely failure mode(s)

Safety assessment

Clarity score

Actionability score

~community cookbook

~you might also like

ship

doc-author

multi-agent-architect

tangram-execute

autonomous-agent-patterns

security-suite

AI Skill Finder

kubernetes-skill

Key Features

Use Cases

Best for

Not ideal for

FAQs

Which Kubernetes distributions are supported?

Does this work for Helm charts?

What failure modes does it check?

Is cluster access required?

KubeShark: Failure-Mode Workflow for Kubernetes

1) Capture execution context

2) Diagnose likely failure mode(s)

Safety assessment

Clarity score

Actionability score

~community cookbook

~you might also like

ship

doc-author

multi-agent-architect

tangram-execute

autonomous-agent-patterns

security-suite