How do I install the Kubernetes Helm skill?

Run npx skillmds@latest add blogic-cz/kubernetes-helm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubernetes Helm safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubernetes Helm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubernetes Helm free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubernetes Helm?

blogic-cz (@blogic-cz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubernetes Helm by blogic-cz — Agent Skill

Name: Kubernetes Helm
Author: blogic-cz

Kubernetes Helm

This skill should be used when working on Kubernetes or Helm changes in template-ts projects, including values files, env vars, secrets, ingress, resources, hooks, namespaces, pods, and environment-specific deployment settings.

blogic-cz 1738022 3 files · 6.5 KB Updated Sep 17, 2026

File contents

Kubernetes & Helm Workflow

Apply consistent Helm patterns for test and production Kubernetes environments.

Use this skill when

Update Helm values files
Add or change environment variables
Configure resources, probes, ingress, security, jobs, or cronjobs
Work with Kubernetes secrets, namespaces, pods, and environment URLs

Follow this workflow

Locate the target chart in kubernetes/helm/ and edit both values.test.yaml and values.prod.yaml unless the change is environment-specific.
Add non-sensitive variables under extraEnvVars with direct value; keep entries alphabetically sorted.
Add sensitive variables with valueFrom.secretKeyRef; never inline secrets in values files.
Define hook/job secrets through the chart values key hooks.secretName (in values.*.yaml), then consume it in hook templates (for example migration/sync jobs).
If the repository uses local env files, mirror new variables in .env.example and .env with safe placeholder defaults.
Check chart-specific secret naming and namespace conventions before deploying.
Use k8s-tool for runtime checks only after prerequisites are met: k8s-tool is a project wrapper around kubectl with environment shortcuts, and requires an installed CLI plus valid kubeconfig/cluster access.

Reference material

Read concrete snippets and YAML examples in:

references/chart-structure.md
references/helm-examples.md

Key Rules

Keep extraEnvVars alphabetically sorted
Never commit secrets - use K8s secrets with secretKeyRef
Test values are conservative - lower resources than prod
Use appropriate probe paths - /api/alive for liveness, /api/health for readiness
CronJobs need concurrencyPolicy: Forbid to prevent overlapping

---name: kubernetes-helmdescription: This skill should be used when working on Kubernetes or Helm changes in template-ts projects, including values files, env vars, secrets, ingress, resources, hooks, namespaces, pods, and environment-specific deployment settings.---# Kubernetes & Helm WorkflowApply consistent Helm patterns for test and production Kubernetes environments.## Use this skill when- Update Helm values files- Add or change environment variables- Configure resources, probes, ingress, security, jobs, or cronjobs- Work with Kubernetes secrets, namespaces, pods, and environment URLs## Follow this workflow1. Locate the target chart in `kubernetes/helm/` and edit both `values.test.yaml` and `values.prod.yaml` unless the change is environment-specific.2. Add non-sensitive variables under `extraEnvVars` with direct `value`; keep entries alphabetically sorted.3. Add sensitive variables with `valueFrom.secretKeyRef`; never inline secrets in values files.4. Define hook/job secrets through the chart values key `hooks.secretName` (in `values.*.yaml`), then consume it in hook templates (for example migration/sync jobs).5. If the repository uses local env files, mirror new variables in `.env.example` and `.env` with safe placeholder defaults.6. Check chart-specific secret naming and namespace conventions before deploying.7. Use `k8s-tool` for runtime checks only after prerequisites are met: `k8s-tool` is a project wrapper around `kubectl` with environment shortcuts, and requires an installed CLI plus valid kubeconfig/cluster access.## Reference materialRead concrete snippets and YAML examples in:- `references/chart-structure.md`- `references/helm-examples.md`## Key Rules1. **Keep extraEnvVars alphabetically sorted**2. **Never commit secrets** - use K8s secrets with `secretKeyRef`3. **Test values are conservative** - lower resources than prod4. **Use appropriate probe paths** - `/api/alive` for liveness, `/api/health` for readiness5. **CronJobs need `concurrencyPolicy: Forbid`** to prevent overlapping

Frequently asked questions