What problem does it solve? Writing and maintaining Helm charts often leads to inconsistent naming, insecure defaults, broken templates, and failed deployments. This Skill provides a structured set of standards so charts are secure, deterministic, and easy to maintain across teams. ## Core Features & Use Cases - Chart Structure Standards: Enforces lowercase hyphenated names, SemVer chart versions, quoted appVersion, and namespaced helper templates to avoid collisions. - Values & Schema Guidance: Promotes documented value names, correct typing, values.schema.json for non-trivial surfaces, and required-value validation with clear errors. - Security & Verification: Covers non-root containers, dropped capabilities, read-only filesystems, least-privilege RBAC, probes, and verification via helm lint, helm template, and dry-run tests. - Use Case: When creating a new microservice chart, apply these standards to produce a secure, GitOps-friendly chart that passes linting and renders deterministically before deployment. ## Quick Start Review my Helm chart and apply the Helm standards to fix security, values, and templating issues.