[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BTNJZK12MMVA7ZNF3B6SWX":3,"skill-same:01M7BTNJZK12MMVA7ZNF3B6SWX":69},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7BTNJZK12MMVA7ZNF3B6SWX","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.","azhri1990\u002Fproject-genesis","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7BMC0XAE6SV0VTKWP3EMFGZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fhelm-chart-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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: Alireza Rezvani\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\u002Falirezarezvani\u002Fclaude-skills.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\u002Falirezarezvani\u002Fclaude-skills.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":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1773532800000,"1.0.0","engineering","main","456c0680145b74fe0168cc63541f08eda89e53c0","claude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fhelm-chart-builder","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-09-27 20:56:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add azhri1990\u002Fproject-genesis --skill helm-chart-builder",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fproject-genesis --skill helm-chart-builder",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fproject-genesis --skill helm-chart-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fhelm-chart-builder\u002FSKILL.md",true,[49,55,59,65],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fchart-patterns.md","REFERENCE","参考文档",11818,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fhelm-chart-builder\u002Freferences\u002Fchart-patterns.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fvalues-design.md",9736,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fhelm-chart-builder\u002Freferences\u002Fvalues-design.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Fchart_analyzer.py","SCRIPT","脚本",20022,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fhelm-chart-builder\u002Fscripts\u002Fchart_analyzer.py",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fvalues_validator.py",14524,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.hermes\u002Fskills\u002Fclaude-skills\u002Fengineering\u002Fhelm-chart-builder\u002Fscripts\u002Fvalues_validator.py",[70,77,84,91,98,105],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7C0EZY9FK6JW3YAC7CN17KY","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7C0EA12FWRZTMG0N23HV68M","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7C0DXEHJKMKTB4N6B7MS4BT","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7C0DJM5ECEKZXTQA9G6YHQZ","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7C0D304Z7YX7J25R42N6W2T","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7C0CP1419VDF6SGCDY6ZRZV","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]