Individual skill

helm-k8s-manifest-reviewer

Checks Kubernetes manifests and Helm charts for resource limits, readiness probes, and security contexts.

skills/utilities/helm-k8s-manifest-reviewer/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Audit Kubernetes manifests (Deployments, Services, Ingress, HPAs) and Helm charts for production readiness, proper resource requests/limits, liveness/readiness probes, pod disruption budgets (PDB), and security context hardening.

## When to Use

- Preparing a new service for deployment onto a Kubernetes cluster.
- Auditing Helm chart templates before release.
- Diagnosing CrashLoopBackOff, sudden pod evictions, or traffic drops during rolling deployments.

## What to Analyze

1. **Resource Specifications**: Explicit `requests` (for scheduling) and `limits` (to prevent node exhaustion) for CPU/memory.
2. **Health Probes**: Distinct `livenessProbe` (restarts hung container), `readinessProbe` (controls traffic routing), and `startupProbe` (slow boots).