helm

Applies Helm chart best practices for Kubernetes templating, security, and maintainability.

1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/Fidasek009/agents --skill helm-fidasek009
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helm
Source: https://github.com/Fidasek009/agents/tree/main/.kilo/skills/helm
Command: npx skills add https://github.com/Fidasek009/agents --skill helm-fidasek009

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about helm

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

FAQPage Schema
How do I write a secure Helm chart for Kubernetes?▼

Use non-root containers, dropped capabilities, read-only filesystems, and explicit security contexts in your pod specs. Keep plaintext secrets out of values.yaml and templates, set resource requests and limits, and keep RBAC least-privilege with documented wildcard usage.

How do I validate Helm chart values before deployment?▼

Define a values.schema.json when your chart has a non-trivial public values surface to enforce types and required fields. Additionally, require mandatory values at template time with clear error messages so misconfigurations fail early.

How do I test Helm charts before installing them?▼

Run helm lint and helm template for any changed charts to catch syntax and rendering issues. Use dry-run installs or chart tests when changing install or upgrade behavior to verify the rendered manifests.

Why should Helm templates be deterministic for GitOps?▼

GitOps controllers continuously reconcile rendered manifests, so non-deterministic templates cause endless drift and spurious updates. Keep templates deterministic, apply labels and selectors consistently through helpers, and use tpl only for intentionally supported user-supplied templates.

What naming conventions should Helm charts follow?▼

Use lowercase hyphenated chart names, keep the chart version SemVer-compliant, and quote appVersion since it is a string. Namespace helper template names with the chart name to avoid collisions when charts are used as subcharts.