[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBCPS9XJR45G1C0SHR6AC7":3,"skill-same:01M6KBCPS9XJR45G1C0SHR6AC7":117},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":40,"publishedAt":61,"linkOnly":62,"markdownContent":63,"markdownBody":64,"frontMatter":65,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":74,"repositoryHtmlUrl":75,"repositoryHomepageUrl":6,"ownerHtmlUrl":76,"ownerBlogUrl":77,"ownerDescription":6,"updatedAt":78,"install":79,"resources":92},"01M6KBCPS9XJR45G1C0SHR6AC7","helm-chart-builder",null,"Helm chart development agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw — chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing. Use when: user wants to create or improve Helm charts, design values.yaml files, implement template helpers, audit chart security (RBAC, network policies, pod security), manage subcharts, or run helm lint\u002Ftest.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fhelm-chart-builder\u002FSKILL.md",[18,23,26,29,34,37],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":38,"categoryName":39,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师",[41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60],"chart","chart builder","helm","builder","helm chart builder","template","helm charts","chart testing","scaffolding","files","helm chart development","dependency","testing","improve","Charts","audit","code","create","cli","design","2026-11-10 10:12:30",false,"---\nname: \"helm-chart-builder\"\ndescription: \"Helm chart development agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw — chart scaffolding, values design, template patterns, dependency management, security hardening, and chart testing. Use when: user wants to create or improve Helm charts, design values.yaml files, implement template helpers, audit chart security (RBAC, network policies, pod security), manage subcharts, or run helm lint\u002Ftest.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Md Faiz Alam\n  category: engineering\n  updated: 2026-03-15\n---\n\n# Helm Chart Builder\n\n> Production-grade Helm charts. Sensible defaults. Secure by design. No cargo-culting.\n\nOpinionated Helm workflow that turns ad-hoc Kubernetes manifests into maintainable, testable, reusable charts. Covers chart structure, values design, template patterns, dependency management, and security hardening.\n\nNot a Helm tutorial — a set of concrete decisions about how to build charts that operators trust and developers don't fight.\n\n---\n\n## Slash Commands\n\n| Command | What it does |\n|---------|-------------|\n| `\u002Fhelm:create` | Scaffold a production-ready Helm chart with best-practice structure |\n| `\u002Fhelm:review` | Analyze an existing chart for issues — missing labels, hardcoded values, template anti-patterns |\n| `\u002Fhelm:security` | Audit chart for security issues — RBAC, network policies, pod security, secrets handling |\n\n---\n\n## When This Skill Activates\n\nRecognize these patterns from the user:\n\n- \"Create a Helm chart for this service\"\n- \"Review my Helm chart\"\n- \"Is this chart secure?\"\n- \"Design a values.yaml\"\n- \"Add a subchart dependency\"\n- \"Set up helm tests\"\n- \"Helm best practices for [workload type]\"\n- Any request involving: Helm chart, values.yaml, Chart.yaml, templates, helpers, _helpers.tpl, subcharts, helm lint, helm test\n\nIf the user has a Helm chart or wants to package Kubernetes resources → this skill applies.\n\n---\n\n## Workflow\n\n### `\u002Fhelm:create` — Chart Scaffolding\n\n1. **Identify workload type**\n   - Web service (Deployment + Service + Ingress)\n   - Worker (Deployment, no Service)\n   - CronJob (CronJob + ServiceAccount)\n   - Stateful service (StatefulSet + PVC + Headless Service)\n   - Library chart (no templates, only helpers)\n\n2. **Scaffold chart structure**\n\n   ```\n   mychart\u002F\n   ├── Chart.yaml              # Chart metadata and dependencies\n   ├── values.yaml             # Default configuration\n   ├── values.schema.json      # Optional: JSON Schema for values validation\n   ├── .helmignore             # Files to exclude from packaging\n   ├── templates\u002F\n   │   ├── _helpers.tpl        # Named templates and helper functions\n   │   ├── deployment.yaml     # Workload resource\n   │   ├── service.yaml        # Service exposure\n   │   ├── ingress.yaml        # Ingress (if applicable)\n   │   ├── serviceaccount.yaml # ServiceAccount\n   │   ├── hpa.yaml            # HorizontalPodAutoscaler\n   │   ├── pdb.yaml            # PodDisruptionBudget\n   │   ├── networkpolicy.yaml  # NetworkPolicy\n   │   ├── configmap.yaml      # ConfigMap (if needed)\n   │   ├── secret.yaml         # Secret (if needed)\n   │   ├── NOTES.txt           # Post-install usage instructions\n   │   └── tests\u002F\n   │       └── test-connection.yaml\n   └── charts\u002F                 # Subcharts (dependencies)\n   ```\n\n3. **Apply Chart.yaml best practices**\n\n   ```\n   METADATA\n   ├── apiVersion: v2 (Helm 3 only — never v1)\n   ├── name: matches directory name exactly\n   ├── version: semver (chart version, not app version)\n   ├── appVersion: application version string\n   ├── description: one-line summary of what the chart deploys\n   └── type: application (or library for shared helpers)\n\n   DEPENDENCIES\n   ├── Pin dependency versions with ~X.Y.Z (patch-level float)\n   ├── Use condition field to make subcharts optional\n   ├── Use alias for multiple instances of same subchart\n   └── Run helm dependency update after changes\n   ```\n\n4. **Generate values.yaml with documentation**\n   - Every value has an inline comment explaining purpose and type\n   - Sensible defaults that work for development\n   - Override-friendly structure (flat where possible, nested only when logical)\n   - No hardcoded cluster-specific values (image registry, domain, storage class)\n\n5. **Validate**\n   ```bash\n   python3 scripts\u002Fchart_analyzer.py mychart\u002F\n   helm lint mychart\u002F\n   helm template mychart\u002F --debug\n   ```\n\n### `\u002Fhelm:review` — Chart Analysis\n\n1. **Check chart structure**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Missing _helpers.tpl | High | Create helpers for common labels and selectors |\n   | No NOTES.txt | Medium | Add post-install instructions |\n   | No .helmignore | Low | Create one to exclude .git, CI files, tests |\n   | Missing Chart.yaml fields | Medium | Add description, appVersion, maintainers |\n   | Hardcoded values in templates | High | Extract to values.yaml with defaults |\n\n2. **Check template quality**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Missing standard labels | High | Use `app.kubernetes.io\u002F*` labels via _helpers.tpl |\n   | No resource requests\u002Flimits | Critical | Add resources section with defaults in values.yaml |\n   | Hardcoded image tag | High | Use `{{ .Values.image.repository }}:{{ .Values.image.tag }}` |\n   | No imagePullPolicy | Medium | Default to `IfNotPresent`, overridable |\n   | Missing liveness\u002Freadiness probes | High | Add probes with configurable paths and ports |\n   | No pod anti-affinity | Medium | Add preferred anti-affinity for HA |\n   | Duplicate template code | Medium | Extract into named templates in _helpers.tpl |\n\n3. **Check values.yaml quality**\n   ```bash\n   python3 scripts\u002Fvalues_validator.py mychart\u002Fvalues.yaml\n   ```\n\n4. **Generate review report**\n   ```\n   HELM CHART REVIEW — [chart name]\n   Date: [timestamp]\n\n   CRITICAL: [count]\n   HIGH:     [count]\n   MEDIUM:   [count]\n   LOW:      [count]\n\n   [Detailed findings with fix recommendations]\n   ```\n\n### `\u002Fhelm:security` — Security Audit\n\n1. **Pod security audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | No securityContext | Critical | Add runAsNonRoot, readOnlyRootFilesystem |\n   | Running as root | Critical | Set `runAsNonRoot: true`, `runAsUser: 1000` |\n   | Writable root filesystem | High | Set `readOnlyRootFilesystem: true` + emptyDir for tmp |\n   | All capabilities retained | High | Drop ALL, add only specific needed caps |\n   | Privileged container | Critical | Set `privileged: false`, use specific capabilities |\n   | No seccomp profile | Medium | Set `seccompProfile.type: RuntimeDefault` |\n   | allowPrivilegeEscalation true | High | Set `allowPrivilegeEscalation: false` |\n\n2. **RBAC audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | No ServiceAccount | Medium | Create dedicated SA, don't use default |\n   | automountServiceAccountToken true | Medium | Set to false unless pod needs K8s API access |\n   | ClusterRole instead of Role | Medium | Use namespace-scoped Role unless cluster-wide needed |\n   | Wildcard permissions | Critical | Use specific resource names and verbs |\n   | No RBAC at all | Low | Acceptable if pod doesn't need K8s API access |\n\n3. **Network and secrets audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | No NetworkPolicy | Medium | Add default-deny ingress + explicit allow rules |\n   | Secrets in values.yaml | Critical | Use external secrets operator or sealed-secrets |\n   | No PodDisruptionBudget | Medium | Add PDB with minAvailable for HA workloads |\n   | hostNetwork: true | High | Remove unless absolutely required (e.g., CNI plugin) |\n   | hostPID or hostIPC | Critical | Never use in application charts |\n\n4. **Generate security report**\n   ```\n   SECURITY AUDIT — [chart name]\n   Date: [timestamp]\n\n   CRITICAL: [count]\n   HIGH:     [count]\n   MEDIUM:   [count]\n   LOW:      [count]\n\n   [Detailed findings with remediation steps]\n   ```\n\n---\n\n## Tooling\n\n### `scripts\u002Fchart_analyzer.py`\n\nCLI utility for static analysis of Helm chart directories.\n\n**Features:**\n- Chart structure validation (required files, directory layout)\n- Template anti-pattern detection (hardcoded values, missing labels, no resource limits)\n- Chart.yaml metadata checks\n- Standard labels verification (app.kubernetes.io\u002F*)\n- Security baseline checks\n- JSON and text output\n\n**Usage:**\n```bash\n# Analyze a chart directory\npython3 scripts\u002Fchart_analyzer.py mychart\u002F\n\n# JSON output\npython3 scripts\u002Fchart_analyzer.py mychart\u002F --output json\n\n# Security-focused analysis\npython3 scripts\u002Fchart_analyzer.py mychart\u002F --security\n```\n\n### `scripts\u002Fvalues_validator.py`\n\nCLI utility for validating values.yaml against best practices.\n\n**Features:**\n- Documentation coverage (inline comments)\n- Type consistency checks\n- Hardcoded secrets detection\n- Default value quality analysis\n- Structure depth analysis\n- Naming convention validation\n- JSON and text output\n\n**Usage:**\n```bash\n# Validate values.yaml\npython3 scripts\u002Fvalues_validator.py values.yaml\n\n# JSON output\npython3 scripts\u002Fvalues_validator.py values.yaml --output json\n\n# Strict mode (fail on warnings)\npython3 scripts\u002Fvalues_validator.py values.yaml --strict\n```\n\n---\n\n## Template Patterns\n\n### Pattern 1: Standard Labels (_helpers.tpl)\n\n```yaml\n{{\u002F*\nCommon labels for all resources.\n*\u002F}}\n{{- define \"mychart.labels\" -}}\nhelm.sh\u002Fchart: {{ include \"mychart.chart\" . }}\napp.kubernetes.io\u002Fname: {{ include \"mychart.name\" . }}\napp.kubernetes.io\u002Finstance: {{ .Release.Name }}\napp.kubernetes.io\u002Fversion: {{ .Chart.AppVersion | quote }}\napp.kubernetes.io\u002Fmanaged-by: {{ .Release.Service }}\n{{- end }}\n\n{{\u002F*\nSelector labels (subset of common labels — must be immutable).\n*\u002F}}\n{{- define \"mychart.selectorLabels\" -}}\napp.kubernetes.io\u002Fname: {{ include \"mychart.name\" . }}\napp.kubernetes.io\u002Finstance: {{ .Release.Name }}\n{{- end }}\n```\n\n### Pattern 2: Conditional Resources\n\n```yaml\n{{- if .Values.ingress.enabled -}}\napiVersion: networking.k8s.io\u002Fv1\nkind: Ingress\nmetadata:\n  name: {{ include \"mychart.fullname\" . }}\n  labels:\n    {{- include \"mychart.labels\" . | nindent 4 }}\n  {{- with .Values.ingress.annotations }}\n  annotations:\n    {{- toYaml . | nindent 4 }}\n  {{- end }}\nspec:\n  {{- if .Values.ingress.tls }}\n  tls:\n    {{- range .Values.ingress.tls }}\n    - hosts:\n        {{- range .hosts }}\n        - {{ . | quote }}\n        {{- end }}\n      secretName: {{ .secretName }}\n    {{- end }}\n  {{- end }}\n  rules:\n    {{- range .Values.ingress.hosts }}\n    - host: {{ .host | quote }}\n      http:\n        paths:\n          {{- range .paths }}\n          - path: {{ .path }}\n            pathType: {{ .pathType }}\n            backend:\n              service:\n                name: {{ include \"mychart.fullname\" $ }}\n                port:\n                  number: {{ $.Values.service.port }}\n          {{- end }}\n    {{- end }}\n{{- end }}\n```\n\n### Pattern 3: Security-Hardened Pod Spec\n\n```yaml\nspec:\n  serviceAccountName: {{ include \"mychart.serviceAccountName\" . }}\n  automountServiceAccountToken: false\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    fsGroup: 1000\n    seccompProfile:\n      type: RuntimeDefault\n  containers:\n    - name: {{ .Chart.Name }}\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      image: \"{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}\"\n      imagePullPolicy: {{ .Values.image.pullPolicy }}\n      resources:\n        {{- toYaml .Values.resources | nindent 8 }}\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n---\n\n## Values Design Principles\n\n```\nSTRUCTURE\n├── Flat over nested (image.tag > container.spec.image.tag)\n├── Group by resource (service.*, ingress.*, resources.*)\n├── Use enabled: true\u002Ffalse for optional resources\n├── Document every key with inline YAML comments\n└── Provide sensible development defaults\n\nNAMING\n├── camelCase for keys (replicaCount, not replica_count)\n├── Boolean keys: use adjectives (enabled, required) not verbs\n├── Nested keys: max 3 levels deep\n└── Match upstream conventions (image.repository, image.tag, image.pullPolicy)\n\nANTI-PATTERNS\n├── Hardcoded cluster URLs or domains\n├── Secrets as default values\n├── Empty strings where null is correct\n├── Deeply nested structures (>3 levels)\n├── Undocumented values\n└── values.yaml that doesn't work without overrides\n```\n\n---\n\n## Dependency Management\n\n```\nSUBCHARTS\n├── Use Chart.yaml dependencies (not requirements.yaml — Helm 3)\n├── Pin versions: version: ~15.x.x (patch float)\n├── Use condition: to make optional: condition: postgresql.enabled\n├── Use alias: for multiple instances of same chart\n├── Override subchart values under subchart name key in values.yaml\n└── Run helm dependency update before packaging\n\nLIBRARY CHARTS\n├── type: library in Chart.yaml — no templates directory\n├── Export named templates only — no rendered resources\n├── Use for shared labels, annotations, security contexts\n└── Version independently from application charts\n```\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **No _helpers.tpl** → Create one. Every chart needs standard labels and fullname helpers.\n- **Hardcoded image tag in template** → Extract to values.yaml. Tags must be overridable.\n- **No resource requests\u002Flimits** → Add them. Pods without limits can starve the node.\n- **Running as root** → Add securityContext. No exceptions for production charts.\n- **No NOTES.txt** → Create one. Users need post-install instructions.\n- **Secrets in values.yaml defaults** → Remove them. Use placeholders with comments explaining how to provide secrets.\n- **No liveness\u002Freadiness probes** → Add them. Kubernetes needs to know if the pod is healthy.\n- **Missing app.kubernetes.io labels** → Add via _helpers.tpl. Required for proper resource tracking.\n\n---\n\n## Installation\n\n### One-liner (any tool)\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill.git\ncp -r claude-skills\u002Fengineering\u002Fhelm-chart-builder ~\u002F.claude\u002Fskills\u002F\n```\n\n### Multi-tool install\n```bash\n.\u002Fscripts\u002Fconvert.sh --skill helm-chart-builder --tool codex|gemini|cursor|windsurf|openclaw\n```\n\n### OpenClaw\n```bash\nclawhub install cs-helm-chart-builder\n```\n\n---\n\n## Related Skills\n\n- **senior-devops** — Broader DevOps scope (CI\u002FCD, IaC, monitoring). Complementary — use helm-chart-builder for chart-specific work, senior-devops for pipeline and infrastructure.\n- **docker-development** — Container building. Complementary — docker-development builds the images, helm-chart-builder deploys them to Kubernetes.\n- **ci-cd-pipeline-builder** — Pipeline construction. Complementary — helm-chart-builder defines the deployment artifact, ci-cd-pipeline-builder automates its delivery.\n- **senior-security** — Application security. Complementary — helm-chart-builder covers Kubernetes-level security (RBAC, pod security), senior-security covers application-level threats.\n","# Helm Chart Builder\n\n> Production-grade Helm charts. Sensible defaults. Secure by design. No cargo-culting.\n\nOpinionated Helm workflow that turns ad-hoc Kubernetes manifests into maintainable, testable, reusable charts. Covers chart structure, values design, template patterns, dependency management, and security hardening.\n\nNot a Helm tutorial — a set of concrete decisions about how to build charts that operators trust and developers don't fight.\n\n---\n\n## Slash Commands\n\n| Command | What it does |\n|---------|-------------|\n| `\u002Fhelm:create` | Scaffold a production-ready Helm chart with best-practice structure |\n| `\u002Fhelm:review` | Analyze an existing chart for issues — missing labels, hardcoded values, template anti-patterns |\n| `\u002Fhelm:security` | Audit chart for security issues — RBAC, network policies, pod security, secrets handling |\n\n---\n\n## When This Skill Activates\n\nRecognize these patterns from the user:\n\n- \"Create a Helm chart for this service\"\n- \"Review my Helm chart\"\n- \"Is this chart secure?\"\n- \"Design a values.yaml\"\n- \"Add a subchart dependency\"\n- \"Set up helm tests\"\n- \"Helm best practices for [workload type]\"\n- Any request involving: Helm chart, values.yaml, Chart.yaml, templates, helpers, _helpers.tpl, subcharts, helm lint, helm test\n\nIf the user has a Helm chart or wants to package Kubernetes resources → this skill applies.\n\n---\n\n## Workflow\n\n### `\u002Fhelm:create` — Chart Scaffolding\n\n1. **Identify workload type**\n   - Web service (Deployment + Service + Ingress)\n   - Worker (Deployment, no Service)\n   - CronJob (CronJob + ServiceAccount)\n   - Stateful service (StatefulSet + PVC + Headless Service)\n   - Library chart (no templates, only helpers)\n\n2. **Scaffold chart structure**\n\n   ```\n   mychart\u002F\n   ├── Chart.yaml              # Chart metadata and dependencies\n   ├── values.yaml             # Default configuration\n   ├── values.schema.json      # Optional: JSON Schema for values validation\n   ├── .helmignore             # Files to exclude from packaging\n   ├── templates\u002F\n   │   ├── _helpers.tpl        # Named templates and helper functions\n   │   ├── deployment.yaml     # Workload resource\n   │   ├── service.yaml        # Service exposure\n   │   ├── ingress.yaml        # Ingress (if applicable)\n   │   ├── serviceaccount.yaml # ServiceAccount\n   │   ├── hpa.yaml            # HorizontalPodAutoscaler\n   │   ├── pdb.yaml            # PodDisruptionBudget\n   │   ├── networkpolicy.yaml  # NetworkPolicy\n   │   ├── configmap.yaml      # ConfigMap (if needed)\n   │   ├── secret.yaml         # Secret (if needed)\n   │   ├── NOTES.txt           # Post-install usage instructions\n   │   └── tests\u002F\n   │       └── test-connection.yaml\n   └── charts\u002F                 # Subcharts (dependencies)\n   ```\n\n3. **Apply Chart.yaml best practices**\n\n   ```\n   METADATA\n   ├── apiVersion: v2 (Helm 3 only — never v1)\n   ├── name: matches directory name exactly\n   ├── version: semver (chart version, not app version)\n   ├── appVersion: application version string\n   ├── description: one-line summary of what the chart deploys\n   └── type: application (or library for shared helpers)\n\n   DEPENDENCIES\n   ├── Pin dependency versions with ~X.Y.Z (patch-level float)\n   ├── Use condition field to make subcharts optional\n   ├── Use alias for multiple instances of same subchart\n   └── Run helm dependency update after changes\n   ```\n\n4. **Generate values.yaml with documentation**\n   - Every value has an inline comment explaining purpose and type\n   - Sensible defaults that work for development\n   - Override-friendly structure (flat where possible, nested only when logical)\n   - No hardcoded cluster-specific values (image registry, domain, storage class)\n\n5. **Validate**\n   ```bash\n   python3 scripts\u002Fchart_analyzer.py mychart\u002F\n   helm lint mychart\u002F\n   helm template mychart\u002F --debug\n   ```\n\n### `\u002Fhelm:review` — Chart Analysis\n\n1. **Check chart structure**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Missing _helpers.tpl | High | Create helpers for common labels and selectors |\n   | No NOTES.txt | Medium | Add post-install instructions |\n   | No .helmignore | Low | Create one to exclude .git, CI files, tests |\n   | Missing Chart.yaml fields | Medium | Add description, appVersion, maintainers |\n   | Hardcoded values in templates | High | Extract to values.yaml with defaults |\n\n2. **Check template quality**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | Missing standard labels | High | Use `app.kubernetes.io\u002F*` labels via _helpers.tpl |\n   | No resource requests\u002Flimits | Critical | Add resources section with defaults in values.yaml |\n   | Hardcoded image tag | High | Use `{{ .Values.image.repository }}:{{ .Values.image.tag }}` |\n   | No imagePullPolicy | Medium | Default to `IfNotPresent`, overridable |\n   | Missing liveness\u002Freadiness probes | High | Add probes with configurable paths and ports |\n   | No pod anti-affinity | Medium | Add preferred anti-affinity for HA |\n   | Duplicate template code | Medium | Extract into named templates in _helpers.tpl |\n\n3. **Check values.yaml quality**\n   ```bash\n   python3 scripts\u002Fvalues_validator.py mychart\u002Fvalues.yaml\n   ```\n\n4. **Generate review report**\n   ```\n   HELM CHART REVIEW — [chart name]\n   Date: [timestamp]\n\n   CRITICAL: [count]\n   HIGH:     [count]\n   MEDIUM:   [count]\n   LOW:      [count]\n\n   [Detailed findings with fix recommendations]\n   ```\n\n### `\u002Fhelm:security` — Security Audit\n\n1. **Pod security audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | No securityContext | Critical | Add runAsNonRoot, readOnlyRootFilesystem |\n   | Running as root | Critical | Set `runAsNonRoot: true`, `runAsUser: 1000` |\n   | Writable root filesystem | High | Set `readOnlyRootFilesystem: true` + emptyDir for tmp |\n   | All capabilities retained | High | Drop ALL, add only specific needed caps |\n   | Privileged container | Critical | Set `privileged: false`, use specific capabilities |\n   | No seccomp profile | Medium | Set `seccompProfile.type: RuntimeDefault` |\n   | allowPrivilegeEscalation true | High | Set `allowPrivilegeEscalation: false` |\n\n2. **RBAC audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | No ServiceAccount | Medium | Create dedicated SA, don't use default |\n   | automountServiceAccountToken true | Medium | Set to false unless pod needs K8s API access |\n   | ClusterRole instead of Role | Medium | Use namespace-scoped Role unless cluster-wide needed |\n   | Wildcard permissions | Critical | Use specific resource names and verbs |\n   | No RBAC at all | Low | Acceptable if pod doesn't need K8s API access |\n\n3. **Network and secrets audit**\n\n   | Check | Severity | Fix |\n   |-------|----------|-----|\n   | No NetworkPolicy | Medium | Add default-deny ingress + explicit allow rules |\n   | Secrets in values.yaml | Critical | Use external secrets operator or sealed-secrets |\n   | No PodDisruptionBudget | Medium | Add PDB with minAvailable for HA workloads |\n   | hostNetwork: true | High | Remove unless absolutely required (e.g., CNI plugin) |\n   | hostPID or hostIPC | Critical | Never use in application charts |\n\n4. **Generate security report**\n   ```\n   SECURITY AUDIT — [chart name]\n   Date: [timestamp]\n\n   CRITICAL: [count]\n   HIGH:     [count]\n   MEDIUM:   [count]\n   LOW:      [count]\n\n   [Detailed findings with remediation steps]\n   ```\n\n---\n\n## Tooling\n\n### `scripts\u002Fchart_analyzer.py`\n\nCLI utility for static analysis of Helm chart directories.\n\n**Features:**\n- Chart structure validation (required files, directory layout)\n- Template anti-pattern detection (hardcoded values, missing labels, no resource limits)\n- Chart.yaml metadata checks\n- Standard labels verification (app.kubernetes.io\u002F*)\n- Security baseline checks\n- JSON and text output\n\n**Usage:**\n```bash\n# Analyze a chart directory\npython3 scripts\u002Fchart_analyzer.py mychart\u002F\n\n# JSON output\npython3 scripts\u002Fchart_analyzer.py mychart\u002F --output json\n\n# Security-focused analysis\npython3 scripts\u002Fchart_analyzer.py mychart\u002F --security\n```\n\n### `scripts\u002Fvalues_validator.py`\n\nCLI utility for validating values.yaml against best practices.\n\n**Features:**\n- Documentation coverage (inline comments)\n- Type consistency checks\n- Hardcoded secrets detection\n- Default value quality analysis\n- Structure depth analysis\n- Naming convention validation\n- JSON and text output\n\n**Usage:**\n```bash\n# Validate values.yaml\npython3 scripts\u002Fvalues_validator.py values.yaml\n\n# JSON output\npython3 scripts\u002Fvalues_validator.py values.yaml --output json\n\n# Strict mode (fail on warnings)\npython3 scripts\u002Fvalues_validator.py values.yaml --strict\n```\n\n---\n\n## Template Patterns\n\n### Pattern 1: Standard Labels (_helpers.tpl)\n\n```yaml\n{{\u002F*\nCommon labels for all resources.\n*\u002F}}\n{{- define \"mychart.labels\" -}}\nhelm.sh\u002Fchart: {{ include \"mychart.chart\" . }}\napp.kubernetes.io\u002Fname: {{ include \"mychart.name\" . }}\napp.kubernetes.io\u002Finstance: {{ .Release.Name }}\napp.kubernetes.io\u002Fversion: {{ .Chart.AppVersion | quote }}\napp.kubernetes.io\u002Fmanaged-by: {{ .Release.Service }}\n{{- end }}\n\n{{\u002F*\nSelector labels (subset of common labels — must be immutable).\n*\u002F}}\n{{- define \"mychart.selectorLabels\" -}}\napp.kubernetes.io\u002Fname: {{ include \"mychart.name\" . }}\napp.kubernetes.io\u002Finstance: {{ .Release.Name }}\n{{- end }}\n```\n\n### Pattern 2: Conditional Resources\n\n```yaml\n{{- if .Values.ingress.enabled -}}\napiVersion: networking.k8s.io\u002Fv1\nkind: Ingress\nmetadata:\n  name: {{ include \"mychart.fullname\" . }}\n  labels:\n    {{- include \"mychart.labels\" . | nindent 4 }}\n  {{- with .Values.ingress.annotations }}\n  annotations:\n    {{- toYaml . | nindent 4 }}\n  {{- end }}\nspec:\n  {{- if .Values.ingress.tls }}\n  tls:\n    {{- range .Values.ingress.tls }}\n    - hosts:\n        {{- range .hosts }}\n        - {{ . | quote }}\n        {{- end }}\n      secretName: {{ .secretName }}\n    {{- end }}\n  {{- end }}\n  rules:\n    {{- range .Values.ingress.hosts }}\n    - host: {{ .host | quote }}\n      http:\n        paths:\n          {{- range .paths }}\n          - path: {{ .path }}\n            pathType: {{ .pathType }}\n            backend:\n              service:\n                name: {{ include \"mychart.fullname\" $ }}\n                port:\n                  number: {{ $.Values.service.port }}\n          {{- end }}\n    {{- end }}\n{{- end }}\n```\n\n### Pattern 3: Security-Hardened Pod Spec\n\n```yaml\nspec:\n  serviceAccountName: {{ include \"mychart.serviceAccountName\" . }}\n  automountServiceAccountToken: false\n  securityContext:\n    runAsNonRoot: true\n    runAsUser: 1000\n    fsGroup: 1000\n    seccompProfile:\n      type: RuntimeDefault\n  containers:\n    - name: {{ .Chart.Name }}\n      securityContext:\n        allowPrivilegeEscalation: false\n        readOnlyRootFilesystem: true\n        capabilities:\n          drop:\n            - ALL\n      image: \"{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}\"\n      imagePullPolicy: {{ .Values.image.pullPolicy }}\n      resources:\n        {{- toYaml .Values.resources | nindent 8 }}\n      volumeMounts:\n        - name: tmp\n          mountPath: \u002Ftmp\n  volumes:\n    - name: tmp\n      emptyDir: {}\n```\n\n---\n\n## Values Design Principles\n\n```\nSTRUCTURE\n├── Flat over nested (image.tag > container.spec.image.tag)\n├── Group by resource (service.*, ingress.*, resources.*)\n├── Use enabled: true\u002Ffalse for optional resources\n├── Document every key with inline YAML comments\n└── Provide sensible development defaults\n\nNAMING\n├── camelCase for keys (replicaCount, not replica_count)\n├── Boolean keys: use adjectives (enabled, required) not verbs\n├── Nested keys: max 3 levels deep\n└── Match upstream conventions (image.repository, image.tag, image.pullPolicy)\n\nANTI-PATTERNS\n├── Hardcoded cluster URLs or domains\n├── Secrets as default values\n├── Empty strings where null is correct\n├── Deeply nested structures (>3 levels)\n├── Undocumented values\n└── values.yaml that doesn't work without overrides\n```\n\n---\n\n## Dependency Management\n\n```\nSUBCHARTS\n├── Use Chart.yaml dependencies (not requirements.yaml — Helm 3)\n├── Pin versions: version: ~15.x.x (patch float)\n├── Use condition: to make optional: condition: postgresql.enabled\n├── Use alias: for multiple instances of same chart\n├── Override subchart values under subchart name key in values.yaml\n└── Run helm dependency update before packaging\n\nLIBRARY CHARTS\n├── type: library in Chart.yaml — no templates directory\n├── Export named templates only — no rendered resources\n├── Use for shared labels, annotations, security contexts\n└── Version independently from application charts\n```\n\n---\n\n## Proactive Triggers\n\nFlag these without being asked:\n\n- **No _helpers.tpl** → Create one. Every chart needs standard labels and fullname helpers.\n- **Hardcoded image tag in template** → Extract to values.yaml. Tags must be overridable.\n- **No resource requests\u002Flimits** → Add them. Pods without limits can starve the node.\n- **Running as root** → Add securityContext. No exceptions for production charts.\n- **No NOTES.txt** → Create one. Users need post-install instructions.\n- **Secrets in values.yaml defaults** → Remove them. Use placeholders with comments explaining how to provide secrets.\n- **No liveness\u002Freadiness probes** → Add them. Kubernetes needs to know if the pod is healthy.\n- **Missing app.kubernetes.io labels** → Add via _helpers.tpl. Required for proper resource tracking.\n\n---\n\n## Installation\n\n### One-liner (any tool)\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill.git\ncp -r claude-skills\u002Fengineering\u002Fhelm-chart-builder ~\u002F.claude\u002Fskills\u002F\n```\n\n### Multi-tool install\n```bash\n.\u002Fscripts\u002Fconvert.sh --skill helm-chart-builder --tool codex|gemini|cursor|windsurf|openclaw\n```\n\n### OpenClaw\n```bash\nclawhub install cs-helm-chart-builder\n```\n\n---\n\n## Related Skills\n\n- **senior-devops** — Broader DevOps scope (CI\u002FCD, IaC, monitoring). Complementary — use helm-chart-builder for chart-specific work, senior-devops for pipeline and infrastructure.\n- **docker-development** — Container building. Complementary — docker-development builds the images, helm-chart-builder deploys them to Kubernetes.\n- **ci-cd-pipeline-builder** — Pipeline construction. Complementary — helm-chart-builder defines the deployment artifact, ci-cd-pipeline-builder automates its delivery.\n- **senior-security** — Application security. Complementary — helm-chart-builder covers Kubernetes-level security (RBAC, pod security), senior-security covers application-level threats.\n",{"name":5,"license":15,"metadata":66,"description":7},{"author":67,"updated":68,"version":69,"category":70},"Md Faiz Alam",1773532800000,"1.0.0","engineering","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","engineering\u002Fhelm-chart-builder",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill helm-chart-builder",{"tool":85,"command":86},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill helm-chart-builder",{"tool":88,"command":89},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill helm-chart-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fhelm-chart-builder\u002FSKILL.md",true,[93,99,103,107,113],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",604,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fhelm-chart-builder\u002F.claude-plugin\u002Fplugin.json",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fchart-patterns.md",11818,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fhelm-chart-builder\u002Freferences\u002Fchart-patterns.md",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fvalues-design.md",9736,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fhelm-chart-builder\u002Freferences\u002Fvalues-design.md",{"path":108,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":111,"sourceHtmlUrl":112},"scripts\u002Fchart_analyzer.py","SCRIPT","脚本",20022,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fhelm-chart-builder\u002Fscripts\u002Fchart_analyzer.py",{"path":114,"resourceType":109,"resourceTypeDesc":110,"sizeBytes":115,"sourceHtmlUrl":116},"scripts\u002Fvalues_validator.py",14524,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fengineering\u002Fhelm-chart-builder\u002Fscripts\u002Fvalues_validator.py",[118,147,172,197,224,244],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":61},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000037","律师与法务",[128,129,130,131,56,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146],"compliance","soc2","soc2 compliance","audit evidence","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":61},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[154,155,156,157,158,159,160,161,134,135,162,163,164,165,166,167,168,169,170,171],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":61},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[179,180,181,182,183,184,185,186,187,135,188,189,190,191,192,193,194,195,196,146],"regulatory affairs head","regulatory","head","documents","devices","health","plan","write","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":61},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[203,206],{"categoryNo":204,"categoryName":205,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},[208,209,196,60,210,211,212,213,214,135,215,216,217,218,219,220,221,222,146,223],"quality manager qms iso13485","quality","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":225,"name":226,"nameZh":6,"description":227,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":228,"categories":229,"keywords":231,"publishedAt":61},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[230],{"categoryNo":125,"categoryName":126,"taxonomyType":32,"taxonomyTypeDesc":33},[232,209,196,233,234,235,236,237,128,238,214,239,180,240,241,242,163,219,146,243],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":248,"categories":249,"keywords":255,"publishedAt":61},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[250,253,254],{"categoryNo":251,"categoryName":252,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":125,"categoryName":126,"taxonomyType":32,"taxonomyTypeDesc":33},[256,257,209,196,233,258,259,56,214,260,261,262,263,264,164,265,266,267,268,146],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]