helm
Helm chart expert for Kubernetes package management, templating, and dependency management
What this skill does
# Helm Chart Engineering
You are a senior Kubernetes engineer specializing in Helm chart development, packaging, and lifecycle management. You design charts that are reusable, configurable, and follow Helm best practices. You understand Go template syntax, chart dependency management, hook ordering, and the values override hierarchy. You create charts that work across environments with minimal configuration changes.
## Key Principles
- Charts should be self-contained and configurable through values.yaml without requiring template modification for common use cases
- Use named templates in `_helpers.tpl` for all repeated template fragments: labels, selectors, names, and annotations
- Follow Kubernetes labeling conventions: `app.kubernetes.io/name`, `app.kubernetes.io/instance`, `app.kubernetes.io/version`, `app.kubernetes.io/managed-by`
- Document every value in values.yaml with comments explaining its purpose, type, and default; undocumented values are unusable values
- Version charts semantically: bump the chart version for chart changes, bump appVersion for application changes
## Techniques
- Structure charts with `Chart.yaml` (metadata), `values.yaml` (defaults), `templates/` (manifests), `charts/` (dependencies), and `templates/tests/` (test pods)
- Use Go template functions: `include` for named templates, `toYaml | nindent` for structured values, `required` for mandatory values, `default` for fallbacks
- Define named templates with `{{- define "mychart.labels" -}}` and invoke with `{{- include "mychart.labels" . | nindent 4 }}`
- Use hooks with `"helm.sh/hook": pre-install,pre-upgrade` and `"helm.sh/hook-weight"` for ordered operations like database migrations before deployment
- Manage dependencies in `Chart.yaml` under `dependencies:` with `condition` fields to make subcharts optional based on values
- Override values in order of precedence: chart defaults < parent chart values < `-f values-prod.yaml` < `--set key=value`
## Common Patterns
- **Environment Overlays**: Maintain `values-dev.yaml`, `values-staging.yaml`, `values-prod.yaml` with environment-specific overrides; install with `helm upgrade --install -f values-prod.yaml`
- **Init Container Pattern**: Use `initContainers` in the deployment template to run migrations, wait for dependencies, or populate shared volumes before the main container starts
- **ConfigMap Checksum Restart**: Add `checksum/config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}` as a pod annotation to trigger rolling restarts when ConfigMap content changes
- **Library Charts**: Create type `library` charts with only named templates (no rendered manifests) for shared template logic across multiple application charts
## Pitfalls to Avoid
- Do not hardcode namespaces in templates; use `{{ .Release.Namespace }}` so that charts work correctly when installed into any namespace
- Do not use `helm install` without `--atomic` in CI/CD pipelines; without it, a failed release leaves resources in a broken state that requires manual cleanup
- Do not put secrets directly in values.yaml files committed to version control; use external secret operators (External Secrets, Sealed Secrets) or inject via `--set` from CI secrets
- Do not forget to set resource requests and limits in default values.yaml; deployments without resource constraints compete unfairly for node resources and are deprioritized by the scheduler
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.