k8s-helm-troubleshooting SKILL.md skillA
k8s-helm-troubleshooting from k8s-servant/k8s-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add k8s-servant/k8s-skills/k8s-helm-troubleshooting@git:20261024.02a7975Pins git:20261024.02a7975 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- k8s-servant/k8s-skills
- Path
skills/k8s-helm-troubleshooting/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261024.02a7975, committed Oct 24, 2026
- Size
- 10,062 bytes
- Repository stars
- 35
- License
- Apache-2.0
Use when a Helm install, upgrade or rollback fails or a release is stuck: "UPGRADE FAILED" or "INSTALLATION FAILED", "context deadline exceeded" or "resource ... not ready" after --wait, "another operation (install/upgrade/rollback) is in progress", a release in pending-install, pending-upgrade or failed state, "exists and cannot be imported into the current release: invalid ownership metadata", "cannot reuse a name that is still in use", "has no deployed releases", hook failures…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Helm troubleshooting Find out why a Helm release fails or is stuck, and propose a fix. **Read first, ask before changing.** Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user. **Helm keeps every release in a Secret** (type `helm.sh/release.v1`, named `sh.helm.release.v1.<release>.v<revision>`), with its values, which often hold passwords. `helm status`, `helm history`, `helm list` and `helm get` all read those Secrets, and you never read Secrets. So you investigate the release's **objects** with kubectl, and you give the `helm` commands to the user to run and paste back. They are under "Proposed fix" only because they read Secrets, not because they change anything; say so when you hand them over. Never ask for `helm get values` output without warning that values can contain passwords the user should remove first. The commands use placeholders: `my-app` (the release), `my-namespace` (its namespace) and `my-app-podinfo` (an object of the release). Replace them with the real names. …
Read the whole file at its exact version.
How to install
mdr add k8s-servant/k8s-skills/k8s-helm-troubleshooting@sha256:69bbd34eec44678aThe line at the top of this page pins the label git:20261024.02a7975, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qqn3vz2fvbb6fvvy)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 24, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10062 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
k8s-servant/k8s-skills · 35 stars · license Apache-2.0 · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qqn3vz2fvbb6fvvy GET https://markdownregistry.com/api/v1/resolve?ref=k8s-servant/k8s-skills/k8s-helm-troubleshooting GET https://markdownregistry.com/api/v1/blob/69bbd34eec44678a9a6a96ea3a6bb37f7bcdd1e0b1d35519c1bddbd1d4d69a80
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.