helmchart

Review, harden, and validate Helm charts with lint and render checks.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill helmchart-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: helmchart
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/helmchart
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill helmchart-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Helm charts often ship with weak security defaults, unpinned images, missing schema validation, and untested templates that break at deploy time. This Skill applies a structured review and hardening workflow so charts render safely and consistently before release. ## Core Features & Use Cases - Chart Hardening: Enforces baseline structure (Chart.yaml, values.yaml, _helpers.tpl), standard labels, fail-fast required values, secure pod/securityContext defaults, and least-privilege RBAC. - Dependency-Aware Validation: Resolves chart dependencies, then runs helm lint --strict and helm template smoke renders, including kube-version and CRD-gated feature checks. - Use Case: Before publishing an internal application chart, run the Skill to pin image tags, externalize secrets, add values.schema.json, split readiness/liveness probes, and verify the rendered manifests against your supported Kubernetes version. ## Quick Start Use the helmchart skill to review and harden the chart in charts/my-app and validate it with helm lint and helm template.

Frequently Asked Questions about helmchart

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a Helm chart before deploying?

Run helm lint with --strict to catch warnings, then helm template with --debug to verify rendered manifests. Resolve dependencies first with helm dependency build or update, and optionally render against a specific Kubernetes version using --kube-version.

How to harden Helm chart security defaults?

Set runAsNonRoot, allowPrivilegeEscalation false, drop all capabilities, and use seccompProfile RuntimeDefault. Disable automountServiceAccountToken unless the workload needs Kubernetes API access, and back writable paths with emptyDir when enabling readOnlyRootFilesystem.

Should chart version match appVersion in Chart.yaml?

No, chart version and appVersion follow independent lifecycles. Keep version as SemVer 2 for the package, and keep appVersion as a quoted informational string aligned with the default application image version when known.

Does helm template work with CRD-dependent features like ServiceMonitor?

Yes, simulate CRDs using --api-versions flags, for example --api-versions monitoring.coreos.com/v1/ServiceMonitor. Charts should gate optional CRD features behind values and fail clearly when required CRDs are missing.

When should I not use this Helm chart skill?

Do not use it for plain Kubernetes manifests, Kustomize, Dockerfiles, or Terraform unless the task explicitly connects them to the chart. For OCI chart publication, use a dedicated publish workflow instead.