helm
Skill4 starsChanged 5 months agoMITView on GitHub
Use when working with Helm — route to the correct sub-skill based on what you need: writing Helm charts or production operations (GitOps, release inspection, OCI, hooks). **Manual helm CLI for prod deploys is NOT recommended — prefer GitOps (Flux, ArgoCD).**
11 other projects use a version of this.
Adopted by
Most recently taken up by
- kaynetik/skillstheir own version, first seen Oct 20, 2026
- air-gapped/skillstheir own version, first seen Oct 19, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- Nicegarrry/claude-skillstheir own version, first seen Oct 13, 2026
- kagenti/kagentitheir own version, first seen Oct 8, 2026
- Jimuelle07/Helmtheir own version, first seen Sep 24, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- kagenti/kagenti★ 303same name
- mjunaidca/mjs-agent-skills★ 27same name
- greedychipmunk/agent-skills★ 24same name
- G1Joshi/Agent-Skills★ 15same name
- Jimuelle07/Helm★ 14same name
- air-gapped/skills★ 6same name
- mattstruble/skills★ 3same name
- kaynetik/skills★ 1same name
- chasey-myagi/helm★ 0same name
- Nicegarrry/claude-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository74 other files it gives its agents.
- AGENTS.mdAGENTS.md
- atlasSkill
- cert-managerSkill
- cilium-gatewaySkill
- cilium-networkSkill
- cnpgSkill
- dragonflySkill
- external-dnsSkill
- external-secretsSkill
- flaggerSkill
- fluxSkill
- gitea-apiSkill
- gitea-registrySkill
- gitea-runnerSkill
- giteaSkill
- gitea-teaSkill
- gitea-webhooksSkill
- harbor-apiSkill
- harbor-helmSkill
- harborSkill
- harbor-terraformSkill
- helm-chartSkill
- helm-opsSkill
- higress-helmSkill
- higress-operatorSkill
- higressSkill
- kserve-helmSkill
- kserve-operatorSkill
- kserveSkill
- kubeflow-pipelinesSkill
- kubeflowSkill
- kubeflow-trainerSkill
- kubeflow-training-operatorSkill
- mariadb-helmSkill
- mariadb-operatorSkill
- mariadbSkill
- netbird-cliSkill
- netbird-operatorSkill
- netbird-serverSkill
- netbirdSkill
- netbird-terraformSkill
- nextcloud-apiSkill
- nextcloud-helmSkill
- nextcloudSkill
- nvidia-device-pluginSkill
- rook-ceph-operatorSkill
- rook-cephSkill
- rook-ceph-toolboxSkill
- sealed-secretsSkill
- stakater-reloaderSkill
- tailscaleSkill
- tailscale-talosSkill
- talosconfigSkill
- talosctlSkill
- talosSkill
- talos-terraformSkill
- tekton-operatorSkill
- tekton-pacSkill
- tekton-pipelinesSkill
- tektonSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
If routing is ambiguous:
- Distinctive: line 53
No server-side component (Helm 3+ client-only).
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Helm — Skill Router
Latest: v4.2.3 (v3.21.3 support until Nov 2026)
⚠️ Production Warning
Do not use helm install / helm upgrade manually or from CI for production. Manual Helm bypasses drift detection, audit trail, Git-as-truth, and rollback-via-revert.
| Use GitOps instead |
Flux: HelmRelease (helm.toolkit.fluxcd.io/v2) |
ArgoCD: Application with Helm source |
Helm CLI is for development, chart writing, debugging, and emergency recovery — not day-2 operations.
Which Sub-Skill?
Match the user's request against the trigger keywords below, then call skill(name="<matched-skill>") to load the sub-skill's full content.
Routing Table
| Trigger keywords | User wants to... | Skill to load |
| chart, template, HelmRelease values, _helpers.tpl, values.yaml, schema, write, create, modify, library chart, chart testing, helm unittest | Write or modify a Helm chart | helm-chart |
| install, upgrade, rollback, inspect, release, status, get values, get manifest, history, failed, troubleshoot, debug, OCI, push, pull, hook, GitOps, Flux, ArgoCD, HelmRelease, drift | Deploy, inspect, or troubleshoot releases | helm-ops |
Decision Tree
If routing is ambiguous:
- User is writing code (templates, YAML, values, helpers) →
helm-chart - User is running commands (install, inspect, debug, push) →
helm-ops - User is asking about both? → Load
helm-chartfirst (chart must exist before deploying), thenhelm-ops
When NOT to load this router
- User question is about a specific product's Helm chart (e.g. Higress, Vault, MariaDB) → load that product's
*-helmskill instead (e.g.higress-helm,vault-helm) - User needs Terraform for Helm releases → load
harbor-terraformor similar - User is working with ArgoCD or Flux generally (not Helm-specific) → load their respective skills
- User just needs a quick CLI reference → router's Quick CLI Reference section below is sufficient
Architecture
Chart → template engine (Go + Sprig) → rendered manifests → kubectl apply (SSA in v4) → release stored in SecretsNo server-side component (Helm 3+ client-only). Releases live as Secrets in the target namespace.
Helm 4 vs 3
| Feature | Helm 3 | Helm 4 |
| Apply mode | Client-side patch | Server-side apply (SSA) default |
--atomic | ✓ | Renamed to --rollback-on-failure |
--force | Delete+recreate pods | Renamed to --force-replace |
| Post-renderer | Arbitrary binary | Plugin name required |
| Status | Bug fixes until Jul 2026, security until Nov 2026 | Current stable |
Quick CLI Reference
| Command | Purpose |
helm install <rel> <chart> -n <ns> | Install (dev/test only) |
helm upgrade --install <rel> <chart> -n <ns> -f vals.yaml | Idempotent install-or-upgrade |
helm rollback <rel> [rev] -n <ns> | Rollback |
helm uninstall <rel> -n <ns> | Delete |
helm list -n <ns> [-a] | List releases |
helm history <rel> -n <ns> | Revision history |
helm status <rel> -n <ns> | Release status |
helm template <rel> ./c -f vals.yaml | Render locally (no cluster) |
helm lint ./c -f vals.yaml | Validate chart structure |
helm get values|manifest|notes|all <rel> -n <ns> | Inspect release |
helm show values|chart|readme|all <chart> | Inspect chart |
helm push .tgz oci://r.example.com/repo | Push to OCI |
helm dep update|build|list | Manage dependencies |
helm test <rel> -n <ns> | Run test pods |
Values Override
| Flag | Example |
-f, --values | -f prod.yaml -f override.yaml (later wins) |
--set | --set image.tag=v2.0 |
--set-string | --set-string image.tag=v2.0.0-rc1 |
Prefer -f over --set. Audit-friendly, composable for environments.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

