Kubernetes Helm Chart Creator skill for Claude and Codex
Produces a minimal, installable Helm chart for one application: Chart.yaml, values.yaml, and templates for the Deployment, Service, and optional Ingress with…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when an app needs a Helm chart from scratch with Deployment, Service, and optional Ingress templates driven by values.yaml. Do not use for editing an existing chart or writing raw Kubernetes manifests without Helm. Related topics: coding, kubernetes, helm.
What it will ask you for
- Application name (free text, e.g. "my-app")
- Replica count (number from 1 to 10)
- Container port (free text, e.g. "80")
- Enable ingress (choose one: Yes, No)
- Hostname (free text, e.g. "app.example.com")
- SSL/TLS enabled (choose one: Yes, No)
How it works
- Lay out Chart.yaml, values.yaml, the helpers template, and one template per resource, with ingress.yaml present only when ingress is enabled.
- Move every tunable into values.yaml and reference it from the templates, so no image, port, or host is hard-coded.
- Wire the Service selector and the Deployment labels through the same helper, so the Service finds the pods.
- Add the Ingress host and TLS block from the inputs when enabled, naming the secret and how it is issued.
- Review the templated output for valid YAML and undefined values so the chart passes helm lint, then deliver the files and the install command.
What you get
One fenced code block per chart file headed by its path (Chart.yaml, values.yaml, templates/_helpers.tpl, templates/deployment.yaml, templates/service.yaml, templates/ingress.yaml when enabled), followed by the helm install command.
What it watches out for
- Hard-coding the image tag in the template instead of values.yaml, so every release needs a chart edit.
- Using different label sets for the Deployment and the Service selector, which leaves the Service with no endpoints.
- Emitting an Ingress with a tls block but no secret, which makes the controller serve a default certificate.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.