jeremylongshore/tons-of-skills-marketplace / plugins/devops/helm-chart-generator/skills/generating-helm-charts
generating-helm-charts
VerifiedExecute use when generating Helm charts for Kubernetes applications. Trigger with phrases like "create Helm chart", "generate chart for app", "package Kubernetes deployment", or "helm template". Produces production-ready charts with Chart.yaml, values.yaml, templates, and best practices for multi-environment deployments.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.4 KB |
| assets/README.md | markdown | 393 B |
| assets/values_schema.json | config | 8.4 KB |
| references/README.md | markdown | 63 B |
| scripts/README.md | markdown | 314 B |
| scripts/helm_create.pyexecutable | script | 3.6 KB |
SKILL.md
View on GitHub---
name: generating-helm-charts
description: 'Execute use when generating Helm charts for Kubernetes applications.
Trigger with phrases like "create Helm chart", "generate chart for app", "package
Kubernetes deployment", or "helm template". Produces production-ready charts with
Chart.yaml, values.yaml, templates, and best practices for multi-environment deployments.
'
allowed-tools: Read, Write, Edit, Grep, Glob, Bash(helm:*), Bash(kubectl:*)
version: 1.25.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- devops
- deployment
- kubernetes
compatibility: Designed for Claude Code
---
# Generating Helm Charts
## Overview
Generate production-ready Helm 3 charts for Kubernetes applications with Chart.yaml, values.yaml, Go templates, and helper functions. Support multi-environment deployments with values overrides, dependency management, security contexts, health probes, and resource limits following Helm best practices.
## Prerequisites
- Helm 3.x installed (`helm version`)
- `kubectl` configured with cluster access for testing chart installation
- Container images available in a registry accessible from the cluster
- Understanding of application resource requirements (CPU, memory, ports, volumes)
- Chart repository access if publishing (ChartMuseum, OCI registry, or GitHub Pages)
## Instructions
1. Analyze the application: identify container images, ports, environment variables, volumes, and dependencies
2. Scaffold the chart structure: `Chart.yaml`, `values.yaml`, `templates/`, `charts/`, `.helmignore`
3. Create `Chart.yaml` with `apiVersion: v2`, name, version, appVersion, and dependency declarations
4. Define `values.yaml` with sensible production defaults: replica count, image config, resource limits, ingress settings
5. Build templates using Go template syntax with proper `.Values` references and `_helpers.tpl` for reusable named templates
6. Add health checks: `livenessProbe` and `readinessProbe` in the deployment template with configurable paths and thresholds
7. Configure security context: `runAsNonRoot: true`, `readOnlyRootFilesystem: true`, and drop all capabilities
8. Create environment-specific values files: `values-dev.yaml`, `values-staging.yaml`, `values-prod.yaml`
9. Add `NOTES.txt` with post-install instructions showing how to access the application
10. Validate with `helm lint .` and test rendering with `helm template . --values values-prod.yaml`
## Output
- Complete Helm chart directory structure
- `Chart.yaml` with metadata and dependencies
- `values.yaml` with documented, configurable defaults
- Template files: `deployment.yaml`, `service.yaml`, `ingress.yaml`, `configmap.yaml`, `serviceaccount.yaml`, `hpa.yaml`
- `_helpers.tpl` with name, label, and selector helper templates
- `NOTES.txt` with post-install access instructions
- Environment-specific values override files
## Error Handling
| Error | Cause | Solution |
|-------|-------|---------|
| `Chart.yaml: version is required` | Missing or malformed `version` field | Add a valid SemVer version string to Chart.yaml |
| `parse error in template` | Go template syntax error (missing `end`, wrong function) | Run `helm template .` to pinpoint the error; check bracket matching and function names |
| `dependency not found` | Chart dependency not downloaded | Run `helm dependency update` to fetch dependencies into `charts/` |
| `release failed: timed out waiting for condition` | Pods not reaching ready state during install | Check pod logs; verify image exists, resource limits are sufficient, and probes are correct |
| `values override not applied` | Wrong values file path or key mismatch | Verify `--values` file path and that keys match the structure in `values.yaml` exactly |
## Examples
- "Generate a Helm chart for a Node.js API with 3 replicas, an Nginx ingress, PostgreSQL subchart dependency, and environment-specific values for dev and prod."
- "Create a Helm chart for a stateful application with PersistentVolumeClaim, headless service, and configurable storage class."
- "Package an existing set of Kubernetes manifests into a Helm chart with parameterized image tag, replica count, and resource limits."
## Resources
- Helm documentation: https://helm.sh/docs/
- Chart best practices: https://helm.sh/docs/chart_best_practices/
- Template function reference: https://helm.sh/docs/chart_template_guide/function_list/
- Artifact Hub (chart discovery): https://artifacthub.io/
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |