helm-charts

Manages Helm chart structure, dependencies, and install/upgrade troubleshooting workflows.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill helm-charts-siegenthalerroger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: helm-charts
Source: https://github.com/siegenthalerroger/.llmctl-marketplace/tree/main/plugins/llmctl-ops-0.2.1/skills/helm-charts
Command: npx skills add https://github.com/siegenthalerroger/.llmctl-marketplace --skill helm-charts-siegenthalerroger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Helm chart work often fails because of incorrect Chart.yaml structure, unmanaged dependencies, or upgrades that silently do not apply. This Skill provides conventions and a verification workflow so chart changes are made against confirmed values rather than assumptions. ## Core Features & Use Cases - Chart Structure Conventions: Enforces correct use of Chart.yaml types, values.schema.json generation via helm-schema, and README generation via helm-docs. - Dependency Management: Guides declaring sub-chart dependencies with conditions, version constraints, and committing Chart.lock. - Verification Workflow: Provides a five-step checklist (inspect values, check current values, render templates, change, dry-run apply) before any helm upgrade. - Use Case: When a helm upgrade is not taking effect, follow the workflow to render templates with helm template, confirm the target field exists in the chart's value schema, and fall back to kubectl patch if the chart does not expose it. ## Quick Start Use the helm-charts skill to diagnose why my helm upgrade is not applying the securityContext field to my deployment.

Frequently Asked Questions about helm-charts

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

FAQPage Schema
How do I add a dependency to a Helm chart?▼

Declare the dependency in Chart.yaml under the dependencies field with a condition so the sub-chart is opt-in. Run helm dependency update afterward and commit the updated Chart.lock to source control.

Why is my helm upgrade not taking effect?▼

The chart template may not expose the field you are setting. Run helm template with your values file and grep for the target field to confirm it renders; if the chart does not wire it up, use kubectl patch instead.

What is the difference between application and library Helm charts?▼

Application charts use type: application and deploy workloads, while library charts use type: library and provide shared named templates only. Library charts are merged at the parent schema level by helm-schema, so avoid property name collisions.

Should I commit Chart.lock to source control?▼

Yes, always commit Chart.lock so dependency versions are reproducible across environments. Never commit unpackaged dependency tarballs.

How do I verify Helm values before upgrading a release?▼

Inspect available values with helm show values, check current values with helm get values --all, render templates with helm template, then apply with helm upgrade --dry-run before the live change.