helm-helper
Helm chart management for Kubernetes deployments When user mentions Helm, charts, helm commands, values, releases, or Kubernetes packaging
What this skill does
# Helm Helper Agent
## What's New in Helm 4.x & 2025
- **OCI Registry Support**: Push/pull charts using `oci://` protocol to container registries
- **Server-Side Dry Run**: Full API validation with `--dry-run=server`
- **JSON Schema Validation**: Validate values with `values.schema.json`
- **Enhanced Diff**: Preview changes with `helm diff` plugin
- **Provenance & Signing**: Sigstore support for chart verification
- **Library Charts**: Reusable chart components with `type: library`
## Overview
Helm is the package manager for Kubernetes. Charts are packages containing Kubernetes resource definitions. Repositories store and share charts. Releases are instances of charts deployed to a cluster.
## CLI Commands
### Auto-Approved Commands
The following `helm` commands are auto-approved and safe to use:
- `helm list` - List releases
- `helm get` - Download release information
- `helm status` - Display release status
- `helm show` - Show chart information
- `helm search` - Search for charts
- `helm version` - Show version info
- `helm env` - Display client environment
- `helm history` - Fetch release history
### Chart Discovery
```bash
# Search Artifact Hub (public charts)
helm search hub nginx
# Search local repositories
helm search repo bitnami/nginx
# Show all versions
helm search repo bitnami/nginx --versions
# Search with version constraints
helm search repo bitnami/nginx --version "^10.0.0"
```
### Installation & Upgrades
```bash
# Basic install
helm install my-release bitnami/nginx
# Install with custom values file
helm install my-release bitnami/nginx -f values.yaml
# Install with inline values
helm install my-release bitnami/nginx --set replicaCount=3
# Install to specific namespace (create if missing)
helm install my-release bitnami/nginx -n production --create-namespace
# Dry run with server-side validation
helm install my-release bitnami/nginx --dry-run=server
# Install with wait and timeout
helm install my-release bitnami/nginx --wait --timeout 5m
# Atomic install (rollback on failure)
helm install my-release bitnami/nginx --atomic
# Install from OCI registry
helm install my-release oci://registry.example.com/charts/nginx --version 1.0.0
```
**Upgrade patterns**:
```bash
# Upgrade existing release
helm upgrade my-release bitnami/nginx -f values.yaml
# Install or upgrade (idempotent)
helm upgrade --install my-release bitnami/nginx
# Reuse previous values and add new ones
helm upgrade my-release bitnami/nginx --reuse-values --set image.tag=v2
# Reset to chart defaults
helm upgrade my-release bitnami/nginx --reset-values
# Rollback on upgrade failure
helm upgrade my-release bitnami/nginx --atomic
# Force replace resources
helm upgrade my-release bitnami/nginx --force
```
### Release Management
```bash
# View release history
helm history my-release
# Rollback to previous revision
helm rollback my-release
# Rollback to specific revision
helm rollback my-release 3
# Uninstall release
helm uninstall my-release
# Uninstall but keep history
helm uninstall my-release --keep-history
```
### Repository Management
```bash
# Add repository
helm repo add bitnami https://charts.bitnami.com/bitnami
# Update repository cache
helm repo update
# List repositories
helm repo list
# Remove repository
helm repo remove bitnami
# Add with credentials
helm repo add private https://charts.example.com --username user --password pass
```
### Chart Development
```bash
# Create new chart
helm create mychart
# Validate chart
helm lint mychart
# Render templates locally
helm template my-release mychart
# Render specific template
helm template my-release mychart --show-only templates/deployment.yaml
# Package chart
helm package mychart
# Package with specific version
helm package mychart --version 1.0.0
# Update dependencies
helm dependency update mychart
# List dependencies
helm dependency list mychart
```
### Information Commands
```bash
# Get all release info
helm get all my-release
# Get deployed values
helm get values my-release
# Get manifest (rendered templates)
helm get manifest my-release
# Get release notes
helm get notes my-release
# Get hooks
helm get hooks my-release
# Show chart info
helm show chart bitnami/nginx
# Show default values
helm show values bitnami/nginx
# Show README
helm show readme bitnami/nginx
```
## Common Workflows
### Install Chart with Custom Values
```bash
# 1. View available values
helm show values bitnami/nginx > default-values.yaml
# 2. Create custom values file
cat > my-values.yaml <<EOF
replicaCount: 3
service:
type: LoadBalancer
resources:
limits:
cpu: 500m
memory: 256Mi
EOF
# 3. Dry run to preview
helm install my-nginx bitnami/nginx -f my-values.yaml --dry-run=server
# 4. Install
helm install my-nginx bitnami/nginx -f my-values.yaml --atomic --wait
```
### Upgrade with Rollback Strategy
```bash
# 1. Check current status
helm status my-release
# 2. Preview changes (requires helm-diff plugin)
helm diff upgrade my-release bitnami/nginx -f new-values.yaml
# 3. Upgrade with automatic rollback on failure
helm upgrade my-release bitnami/nginx -f new-values.yaml --atomic --timeout 10m
# 4. If manual rollback needed
helm rollback my-release 0 # Previous revision
```
### Working with OCI Registries
```bash
# Login to registry
helm registry login registry.example.com
# Push chart to OCI registry
helm push mychart-1.0.0.tgz oci://registry.example.com/charts
# Pull chart
helm pull oci://registry.example.com/charts/mychart --version 1.0.0
# Install from OCI
helm install my-release oci://registry.example.com/charts/mychart --version 1.0.0
# Logout
helm registry logout registry.example.com
```
## Chart Development
### Template Syntax
```yaml
# Access values
{{ .Values.replicaCount }}
# Release information
{{ .Release.Name }}
{{ .Release.Namespace }}
{{ .Release.IsUpgrade }}
# Chart metadata
{{ .Chart.Name }}
{{ .Chart.Version }}
# Common functions
{{ .Values.name | quote }}
{{ .Values.name | upper }}
{{ default "nginx" .Values.image.name }}
{{ required "image.tag is required" .Values.image.tag }}
# Conditionals
{{- if .Values.ingress.enabled }}
# ingress config here
{{- end }}
# Loops
{{- range .Values.hosts }}
- {{ . | quote }}
{{- end }}
```
### Chart.yaml Structure
```yaml
apiVersion: v2
name: mychart
version: 1.0.0
appVersion: "1.16.0"
description: My Helm chart
type: application # or "library"
keywords:
- nginx
- web
dependencies:
- name: postgresql
version: "12.x.x"
repository: https://charts.bitnami.com/bitnami
condition: postgresql.enabled
```
### Values Schema Validation
```json
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": ["replicaCount"],
"properties": {
"replicaCount": {
"type": "integer",
"minimum": 1
},
"image": {
"type": "object",
"properties": {
"repository": { "type": "string" },
"tag": { "type": "string" }
}
}
}
}
```
### Hooks
```yaml
apiVersion: batch/v1
kind: Job
metadata:
name: {{ .Release.Name }}-db-migrate
annotations:
"helm.sh/hook": pre-upgrade,pre-install
"helm.sh/hook-weight": "-5"
"helm.sh/hook-delete-policy": hook-succeeded
spec:
template:
spec:
containers:
- name: migrate
image: migrate:latest
command: ["./migrate.sh"]
restartPolicy: Never
```
Hook types: `pre-install`, `post-install`, `pre-delete`, `post-delete`, `pre-upgrade`, `post-upgrade`, `pre-rollback`, `post-rollback`, `test`
## Best Practices
1. **Always use `--atomic` for production** - Automatic rollback on failure
```bash
helm upgrade --install my-release chart --atomic
```
2. **Pin chart versions** - Never use floating versions
```bash
helm install my-release bitnami/nginx --version 15.0.0
```
3. **Use helm diff before upgrades**
```bash
helm plugin install https://github.com/databus23/helm-diff
helm diff upgrade my-release chart -f vRelated 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.