Kubernetes review
Review Kubernetes manifests and Helm values for security, reliability, and operability. Use whenever the user shares Deployment, Service, Ingress, StatefulSet, Helm charts, or asks about probes, RBAC, resource limits, network policies, or production-ready k8s YAML.From its SKILL.md
npx -y skills add shinzoxD/knackbox --skill kubernetes-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.0 KB, 360 tokens by cl100k_base, as published. Nobody here has run it
Kubernetes Review
Manifests are production config. Prefer secure defaults, clear probes, bounded resources, and least-privilege RBAC.
Review order
- [blocking] privileged pods, hostPath abuse, secrets in env plaintext without need, open RBAC to cluster-admin for apps
- [important] missing probes, no resources, single replica for stateful prod without PDB story, latest tags
- [nit] labels/annotations consistency, naming
Checklist
- Images: pinned tags/digests; pull policy
- SecurityContext: runAsNonRoot, readOnlyRootFilesystem, drop caps
- Probes: liveness vs readiness correctly used
- Resources: requests/limits appropriate
- RBAC: Role vs ClusterRole; least verbs/resources
- Network: Service type, ingress TLS, NetworkPolicy when required
- Rollouts: strategy, PDB, topology spread for critical apps
- Config/Secrets: not committing raw secrets; mounts vs env
Output format
## Kubernetes review
### Findings
1. [blocking] …
### Recommended patches
…
### Verify
kubectl/helm checks
Rules
- Do not invent cluster capabilities (CNI, PSA) — state assumptions.
- Helm: review values and templates for unsafe defaults.
- Separate app bugs from platform policy gaps.
- Prefer concrete YAML diffs over vague "harden it".
- Call out data-loss risks on volume/claim changes.
Edge cases
- Jobs/CronJobs: backoff, concurrency, deadlines.
- Operators/CRDs: review RBAC carefully.
- Local kind/minikube samples: still flag prod-unsafe patterns.
What ships with it: 1 file
1.3 KB alongside SKILL.md
benchmarks/
- prompts.json1.3 KB