Skip to content
Agentmart
Submit a tool

helm-charts

Helm chart development and management for Kubernetes: chart structure, template functions, values and overrides, dependencies, hooks, testing, and packaging…

Skill by dallay

IndexedMIT★ 2
Write a review

Chalk Labs

Need help deploying helm-charts?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/dallay-helm-charts

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Helm chart development and management for Kubernetes: chart structure, template functions, values and overrides, dependencies, hooks, testing, and packaging best practices. Use when the task involves `Helm`, `Helm chart`, `Chart.yaml`, `Helm template`, or `Kubernetes package management`.

Use cases: testing, devops, data, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/helm-charts

What's inside

Skill name
helm-charts
Description
Helm chart development and management for Kubernetes: chart structure, template functions, values and overrides, dependencies, hooks, testing, and packaging best practices. Use when the task involves `Helm`, `Helm chart`, `Chart.yaml`, `Helm template`, or `Kubernetes package management`.
License
MIT
Metadata
version: 1.0.0
Instructions
360 lines in SKILL.md · view on GitHub

Before installing

  • Instructions call the network

Files (1)

  • SKILL.md

SKILL.md (first lines)

## When to Use

- Creating a new Helm chart for a Kubernetes application.
- Writing or reviewing Helm templates (`templates/`, `_helpers.tpl`).
- Managing chart dependencies and multi-chart deployments.
- Configuring hooks for lifecycle events (migrations, backups, cleanup).
- Debugging template rendering issues or failed releases.

## Critical Patterns

- **Named Templates in `_helpers.tpl`:** ALWAYS extract reusable label sets, selectors, and name
  logic into named templates. Duplicating labels across resources is a maintenance trap.
- **Values Schema Validation:** Provide a `values.schema.json` to catch misconfiguration early,
  before templates render invalid YAML.
- **Immutable Selectors:** NEVER change `matchLabels` selectors after initial deployment —
  Kubernetes rejects updates to immutable fields and the release breaks.
- **Quote All Strings in Templates:** Use `{{ .Values.foo | quote }}` for string values to prevent
  YAML type coercion (`"true"` becomes boolean `true` without quotes).
- **Resource Naming Conventions:** Include release name in resource names via
  `{{ include "mychart.fullname" . }}` to support multiple installations in the same namespace.
- **Hook Weight and Delete Policy:** Always set `helm.sh/hook-weight` for ordering and
  `helm.sh/hook-delete-policy` to clean up completed hook resources.

## Code Examples

### Chart Structure

```
mychart/
├── Chart.yaml              # Chart metadata and dependencies
├── Chart.lock              # Locked dependency versions (committed)
├── values.yaml             # Default configuration values
├── values.schema.json      # Optional: JSON Schema for values validation
├── templates/
│   ├── _helpers.tpl        # Named template definitions
│   ├── deployment.yaml
│   ├── service.yaml
│   ├── ingress.yaml
│   ├── configmap.yaml
│   ├── secret.yaml
│   ├── hpa.yaml
│   ├── serviceaccount.yaml
│   └── tests/
│       └── test-connection.yaml
└── charts/                 # Dependency charts (populated by helm dep update)
```

### Chart.yaml

```yaml
apiVersion: v2
name: api-server
description: A Helm chart for the API server application
type: application
version: 0.3.0        # Chart version — bump on template changes
appVersion: "1.2.0"   # Application version — matches container image tag
maintainers:
  - name: platform-team
    email: platform@example.com
dependencies:
  - name: postgresql
    version: "~13.2.0"
    repository: https://charts.bitnami.com/bitnami
    condition: postgresql.enabled
  - name: redis
    version: "~18.6.0"
    repository: https://charts.bitnami.com/bitnami
    condition: redis.enabled
```

### _helpers.tpl — Named Templates

```yaml
{ { /*
  Chart name, truncated to 63 chars (K8s label limit).
  */ } }
  { { - define "mychart.name" - } }
  { { - default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix "-" } }
  { { - end } }

  { { /*
    Fully qualified app name: release-chartname, truncated.
    */ } }
  { { - define "mychart.fullname" - } }
  { { - if .Values.fullnameOverride } }
  { { - .Values.fullnameOverride | trunc 63 | trimSuffix "-" } }
  { { - else } }
  { { - $name := default .Chart.Name .Values.nameOverride } }
  { { - if contains $name .Release.Name } }
  { { - .Release.Name | trunc 63 | trimSuffix "-" } }
  { { - else } }
  { { - printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" } }
  { { - end } }
  { { - end } }
  { { - end } }

  { { /*
    Common labels applied to every resource.
    */ } }
  { { - define "mychart.labels" - } }
helm.sh/chart: { { include "mychart.chart" . } }
  { { include "mychart.selectorLabels" . } }
app.kubernetes.io/version: { { .Chart.AppVersion | quote } }
app.kubernetes.io/managed-by: { { .Release.Service } }
  { { - end } }

  { { /*
    Selector labels — used in both Deployment and Service.
    NEVER change these after first install.
    */ } }
  { { - define "mychart.selectorLabels" - } }
app.kubernetes.io/name: { { include "mychart.name" . } }
app.kubernetes.io/instance: { { .Release.Name } }
  { { - end } }

  { { /*
    Chart label: name-version.
      */ } }
  { { - define "mychart.chart" - } }

From dallay/agents-skills, MIT.

More from dallay/agents-skills

Signals

Stars
2
Forks
0
Open issues
3
Last commit (this folder)
Apr 4, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0.0
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from dallay

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get helm-charts running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying helm-charts?

CallGet help
Cite this page

helm-charts skill. Agent Mart. https://agentmart.dev/skills/dallay-helm-charts (last updated 2026-10-24)