helm
Package and deploy Kubernetes applications with Helm charts and releases. Use when tasks mention helm, Helm charts, helm install, helm upgrade, Helm repositories, values.yaml, or Helm releases.
What this skill does
# helm Use this skill to keep Helm-based Kubernetes deployments reproducible, auditable, and safe across environments. ## Intent Router | Request | Reference | Load When | | --- | --- | --- | | Install Helm, add repos, configure registries | `resources/install-and-setup.md` | User needs to install Helm or configure repositories | | install/upgrade/list/rollback/template commands | `resources/command-cookbook.md` | User needs day-to-day Helm release operations | | Chart.yaml, templates, values, helpers | `resources/chart-authoring.md` | User wants to author or modify a Helm chart | | Release lifecycle, --atomic, --wait, diff plugin | `resources/release-management.md` | User asks about release management or upgrade strategies | ## Quick Start ```bash # Add a chart repository helm repo add bitnami https://charts.bitnami.com/bitnami helm repo update # Search for a chart helm search repo bitnami/nginx # Inspect default values helm show values bitnami/nginx # Install with custom values helm install my-nginx bitnami/nginx --set service.type=ClusterIP -n my-namespace # Upgrade with a values file helm upgrade my-nginx bitnami/nginx -f values.yaml -n my-namespace # List releases helm list -A ``` ## Core Command Tracks - **Install:** `helm install <release> <chart> [flags]` — create a new release - **Upgrade:** `helm upgrade --install <release> <chart>` — create or update release - **Rollback:** `helm rollback <release> [revision]` — revert to previous revision - **Template:** `helm template <release> <chart>` — render manifests locally without applying - **Values:** `helm get values <release>` — inspect values used by a deployed release - **Status:** `helm status <release>` — show release info and notes - **Uninstall:** `helm uninstall <release>` — remove release and resources ## Safety Guardrails - Always run `helm upgrade --dry-run --debug` or `helm template` before applying changes to production. - Use the helm diff plugin (`helm diff upgrade`) to inspect what will change before applying. - Use `--atomic` in CI pipelines so failed upgrades automatically roll back. - Never pass secrets via `--set`; use a secrets manager or the helm-secrets plugin. - Always specify `--namespace` explicitly; do not rely on the default namespace. - Pin chart versions with `--version` in production to ensure reproducibility. - Confirm before running `helm uninstall`; it removes all resources managed by the release. ## Workflow 1. Add and update chart repository: `helm repo add` and `helm repo update`. 2. Inspect default values: `helm show values <chart>`. 3. Create a `values.yaml` override file for environment-specific configuration. 4. Render and review manifests: `helm template <release> <chart> -f values.yaml`. 5. Install or upgrade: `helm upgrade --install <release> <chart> -f values.yaml --atomic --wait`. 6. Verify: `helm list`, `helm status <release>`, `kubectl get pods -n <namespace>`. 7. On failure, check: `helm history <release>` and `helm rollback <release>`. ```bash # Troubleshoot a failed upgrade: inspect history and roll back helm history my-nginx -n my-namespace helm rollback my-nginx 1 -n my-namespace helm status my-nginx -n my-namespace ``` ## Related Skills - **kubectl** — inspect and manage Kubernetes resources created by Helm - **docker** — build container images referenced in Helm chart values ## References - `resources/install-and-setup.md` - `resources/command-cookbook.md` - `resources/chart-authoring.md` - `resources/release-management.md` - Official docs: <https://helm.sh/docs/> - Chart hub: <https://artifacthub.io/>
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.