helm-generator_skill

This skill helps you generate production-ready Helm charts and templates aligned with best practices, enabling rapid creation, validation, and consistent
  • HCL

83

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill akin-ozer/cc-devops-skills --skill helm-generator

  • .gitignore259 B
  • SKILL.md10.0 KB

Overview

This skill is a comprehensive toolkit for generating production-ready Helm charts and Helm resources following current standards and conventions. It scaffolds chart layout, generates standard helpers and templates, and embeds required patterns such as checksum annotations and conditional sections. Use it to produce maintainable charts that pass validation and follow Helm best practices.

How this skill works

The generator collects chart requirements (image, ports, probes, workload type, storage, CRD needs) and scaffolds a standard chart structure with Chart.yaml, values.yaml, values.schema.json, and templates. It emits standard helpers, resource templates (Deployment/StatefulSet/Service/Ingress/etc.), checksum annotations for config restarts, and optional CRD packaging. The workflow mandates validating generated charts with a Helm linter and a dedicated validator skill before delivery.

When to use it

  • Creating a new Helm chart for an application or operator
  • Converting existing Kubernetes manifests into a templated Helm chart
  • Generating consistent templates (deployments, services, ingress, HPA) for a project
  • Adding CRD instances or packaging CRDs for an operator-aware chart
  • When you need charts that must pass linting, schema validation, and rendering checks

Best practices

  • Always ask for missing critical inputs (image, ports, probes, storage, workload type) rather than assuming defaults
  • Include _helpers.tpl with name, fullname, labels, selectorLabels, and serviceAccountName helpers
  • Add checksum annotations for ConfigMap/Secret to trigger pod restarts when config changes
  • Group and document values in values.yaml and provide a values.schema.json for validation
  • Validate generated charts with helm lint, helm template, YAML/schema checks, and an automated validator

Example use cases

  • Scaffold a production chart for a web service with deployment, service, ingress, and HPA templates
  • Convert a set of raw Kubernetes manifests to a reusable Helm chart with parameterized values
  • Package an operator-dependent chart including CRDs in crds/ and templated CR instances in templates/
  • Generate standardized helper templates and labels for multi-chart consistency across a platform
  • Produce charts ready for CI validation and automated linting before publishing to a chart repo

FAQ

I need image repository/tag, service port(s), workload type, resource limits, probe endpoints, scaling requirements, and storage needs if applicable.

How are CRDs handled?

Ship CRD definitions in the crds/ directory (not templated) and place CR instances in templates/; always look up CRD docs for required spec fields.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational