Imported from borghei/claude-skills (engineering/helm-chart-builder/SKILL.md). Install upstream with npx skills add borghei/claude-skills --skill helm-chart-builder. Copyright stays with the author (MIT + Commons Clause).

Helm Chart Builder

Category: Engineering Domain: Kubernetes & Helm

Overview

The Helm Chart Builder skill provides automated analysis of Helm charts including structure validation, values checking, template inspection, and dependency review. It helps teams maintain high-quality charts with correct configurations, proper security contexts, and complete documentation.

Clarify First

Before analyzing the chart, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Chart path — which chart directory to analyze (sets --path/--chart)
• Values files — which environment values files to validate (sets --values and what gets checked against best practices)
• Strictness — strict/lint mode and JSON for CI (sets --strict --format json and whether findings gate the pipeline)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

# Analyze chart structure and quality
python scripts/chart_analyzer.py --path ./charts/my-app

# Validate values.yaml against chart requirements
python scripts/values_validator.py --chart ./charts/my-app --values values-prod.yaml

# JSON output for CI
python scripts/chart_analyzer.py --path ./charts/my-app --format json

# Validate multiple values files
python scripts/values_validator.py --chart ./charts/my-app --values values-dev.yaml values-prod.yaml

Tools Overview

chart_analyzer.py

Analyzes Helm chart structure, metadata, templates, and dependencies.

values_validator.py

Validates values files against chart expectations and Kubernetes best practices.

Workflows

Chart Review Workflow

1. Analyze structure - Run chart_analyzer.py to check chart organization
2. Validate defaults - Run values_validator.py against default values.yaml
3. Check environments - Validate each environment's values file
4. Review findings - Address critical issues first, then warnings
5. Re-check - Confirm fixes pass validation

Pre-Release Workflow

1. Bump version - Update Chart.yaml version and appVersion
2. Lint chart - Run chart_analyzer.py in strict mode
3. Validate all values - Check every environment's values file
4. Check dependencies - Ensure subchart versions are pinned
5. Package - Chart is ready for helm package

CI Integration

# Structure check
python scripts/chart_analyzer.py --path ./charts/my-app --format json --strict

# Values validation for all environments
for env in dev staging production; do
  python scripts/values_validator.py \
    --chart ./charts/my-app \
    --values "values-${env}.yaml"
done

Reference Documentation

• Helm Best Practices - Chart structure, templates, security, dependencies

Common Patterns Quick Reference

Required Chart Structure

my-chart/
  Chart.yaml          # Required: chart metadata
  values.yaml         # Required: default values
  templates/          # Required: template directory
    deployment.yaml
    service.yaml
    _helpers.tpl      # Recommended: template helpers
    NOTES.txt         # Recommended: post-install notes
  charts/             # Optional: subchart dependencies

Values Best Practices

Chart.yaml Required Fields

Common Issues