k8s-helm
Automates Helm chart operations and Kubernetes release management.
Install
mkdir -p .claude/skills/k8s-helm && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1616" && unzip -o skill.zip -d .claude/skills/k8s-helm && rm skill.zipInstalls to .claude/skills/k8s-helm
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Manage Helm charts, releases, and repositories. Use for Helm installations, upgrades, rollbacks, chart development, and release management.Key capabilities
- →Install and upgrade Helm charts
- →Rollback releases to specific revisions
- →Lint and template charts for validation
- →Manage Helm repositories
- →List and inspect release history
How it works
The skill wraps Helm CLI commands to manage the lifecycle of Kubernetes applications through charts, including templating, installation, and history tracking.
Inputs & outputs
When to use k8s-helm
- →Deploy a new Helm chart to a namespace
- →Rollback a failed Helm release
- →Lint and template charts before deployment
About this skill
Helm Chart Management
Comprehensive Helm v3 operations using kubectl-mcp-server's 16 Helm tools.
Requires the
helm_devtoolset: start kubectl-mcp-server with--toolsets default,helm_dev(orMCP_TOOLSETS=default,helm_dev).
When to Apply
Use this skill when:
- User mentions: "helm", "chart", "release", "values", "repository"
- Operations: installing charts, upgrading releases, rollbacks
- Keywords: "package", "template", "lint", "repo add"
Priority Rules
| Priority | Rule | Impact | Tools |
|---|---|---|---|
| 1 | Template before install (dry run) | CRITICAL | helm_template |
| 2 | Check existing releases first | CRITICAL | helm_list |
| 3 | Lint charts before packaging | HIGH | helm_lint |
| 4 | Note revision before upgrade | HIGH | helm_history |
| 5 | Verify values after upgrade | MEDIUM | helm_get |
| 6 | Update repos before search | LOW | helm_repo_update |
Quick Reference
| Task | Tool | Example |
|---|---|---|
| Install chart | install_helm_chart | install_helm_chart(name, chart, namespace) |
| Upgrade release | upgrade_helm_chart | upgrade_helm_chart(name, chart, namespace, values) |
| Rollback | helm_rollback | helm_rollback(name, namespace, revision) |
| List releases | helm_list | helm_list(namespace) |
| Get values | helm_get | helm_get(name, namespace) |
| Template (dry run) | helm_template | helm_template(name, chart, namespace) |
Install Chart
install_helm_chart(
name="my-release",
chart="bitnami/nginx",
namespace="web",
values={"replicaCount": 3, "service.type": "LoadBalancer"}
)
Upgrade Release
upgrade_helm_chart(
name="my-release",
chart="bitnami/nginx",
namespace="web",
values={"replicaCount": 5}
)
Rollback Release
helm_rollback(
release_name="my-release",
namespace="web",
revision=1
)
Uninstall Release
uninstall_helm_chart(name="my-release", namespace="web")
Release Management
List Releases
helm_list(namespace="web")
helm_list()
Get Release Details
helm_status(release_name="my-release", namespace="web")
Release History
helm_history(release_name="my-release", namespace="web")
Get Release Values
helm_get(release_name="my-release", namespace="web")
Get Release Manifest
helm_get(what="manifest", release_name="my-release", namespace="web")
Repository Management
Add Repository
helm_repo_add(name="bitnami", url="https://charts.bitnami.com/bitnami")
List Repositories
helm_repo_list()
Update Repositories
helm_repo_update()
Search Charts
helm_search_repo(keyword="nginx")
helm_search_repo(keyword="bitnami/postgres")
Chart Development
Template Chart (Dry Run)
helm_template(
name="my-release",
chart="./my-chart",
namespace="test",
values={"key": "value"}
)
Lint Chart
helm_lint(chart_path="./my-chart")
Package Chart
helm_package(chart_path="./my-chart", destination="./packages")
Common Workflows
New Application Deployment
helm_repo_add(name="bitnami", url="...")
helm_search_repo(keyword="postgresql")
helm_template(...)
install_helm_chart(...)
helm_status(...)
Upgrade with Rollback Safety
helm_history(name, namespace)
upgrade_helm_chart(name, chart, namespace, values)
helm_rollback(name, namespace, revision)
Multi-Environment Deployment
install_helm_chart(
name="app",
chart="./charts/app",
namespace="dev",
values={"replicas": 1},
context="development"
)
install_helm_chart(
name="app",
chart="./charts/app",
namespace="staging",
values={"replicas": 2},
context="staging"
)
install_helm_chart(
name="app",
chart="./charts/app",
namespace="prod",
values={"replicas": 5},
context="production"
)
Chart Structure
See references/CHART-STRUCTURE.md for best practices on organizing Helm charts.
Troubleshooting
See TROUBLESHOOTING.md for common issues.
Release Stuck in Pending
helm_status(name, namespace)
kubectl_get(resource_type="pods", namespace, label_selector="app.kubernetes.io/instance=<release>")
Failed Installation
helm_history(name, namespace)
kubectl_get(resource_type="events", namespace)
uninstall_helm_chart(name, namespace)
Values Not Applied
helm_get(name, namespace)
helm_template(...)
upgrade_helm_chart(...)
Scripts
See scripts/lint-chart.sh for automated chart validation.
Best Practices
-
Always Template First
helm_template(name, chart, namespace, values) -
Use Semantic Versioning
helm_show(chart="bitnami/nginx", what="chart", version="1.2.3") -
Store Values in Git
values-dev.yamlvalues-staging.yamlvalues-prod.yaml
-
Namespace Isolation
- One namespace per release
- Easier cleanup and RBAC
Prerequisites
- Helm CLI: Required for all Helm operations
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
Related Skills
- k8s-deploy - Deployment strategies
- k8s-gitops - GitOps Helm releases
When not to use it
- →Managing non-Kubernetes applications
- →Directly editing cluster manifests without Helm
Prerequisites
Limitations
- →Requires Helm CLI installed on the host
- →Limited to Helm v3 operations
How it compares
It automates the Helm CLI workflow with structured tool calls instead of manual shell execution.
Compared to similar skills
k8s-helm side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| k8s-helm (this skill) | 8 | 9mo | Review | Intermediate |
| gitops-workflow | 5 | 5mo | Review | Advanced |
| deployment-engineer | 4 | 7mo | No flags | Advanced |
| devops-engineer | 1 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by rohitg00
View all by rohitg00 →You might also like
gitops-workflow
sickn33
Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.
deployment-engineer
sickn33
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.
devops-engineer
Jeffallan
Use when setting up CI/CD pipelines, containerizing applications, or managing infrastructure as code. Invoke for pipelines, Docker, Kubernetes, cloud platforms, GitOps.
platform-engineering
villadalmine
>-
flux
paulpas
"Configures flux in cloud-native engineering - gitops for kubernetes
gitops
pikakit
>-