[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757FWRNAWB49ACFX8Q7GW7F":3,"skill-same:01M757FWRNAWB49ACFX8Q7GW7F":85},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M757FWRNAWB49ACFX8Q7GW7F","helm-expert",null,"Generate production-ready Helm charts with hardened security by default. Use this skill whenever the user needs to create or scaffold a Helm chart, whether they mention it explicitly or are describing Kubernetes deployments that need packaging. The skill ensures security best practices including non-root users, read-only filesystems, network policies, RBAC, Pod Security Standards, and resource limits are all built in from the start. Even if the user just says \"I need to deploy X to Kubernetes\", use this skill to generate a proper Helm chart with hardened defaults.","lukeelten\u002Fpersonal-ai-tooling","lukeelten","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F513392?v=4","01M757ET1X2A4R8NZGQW7T8M1H","Tobias Derksen","01M757ET33H503A8FHPK36TP9M",0,"MIT","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: helm-expert\ndescription: Generate production-ready Helm charts with hardened security by default. Use this skill whenever the user needs to create or scaffold a Helm chart, whether they mention it explicitly or are describing Kubernetes deployments that need packaging. The skill ensures security best practices including non-root users, read-only filesystems, network policies, RBAC, Pod Security Standards, and resource limits are all built in from the start. Even if the user just says \"I need to deploy X to Kubernetes\", use this skill to generate a proper Helm chart with hardened defaults.\n---\n\n# Generating Security-Hardened Helm Charts\n\nThis skill generates production-ready Helm charts with security hardening as the foundation, not an afterthought. All generated charts default to:\n\n- Non-root container users with minimal Linux capabilities\n- Read-only root filesystems (with ephemeral scratch space where needed)\n- Resource requests and limits (CPU, memory)\n- Network policies (restrict ingress\u002Fegress by default)\n- RBAC resources (ServiceAccount, Role\u002FClusterRole, RoleBinding)\n- Pod Security Standards compliance\n- Health checks (livenessProbe, readinessProbe)\n- Image pull policies and security contexts\n\n## Understanding the user's intent\n\nThe user may describe a Kubernetes workload in many ways:\n\n- \"I need a Helm chart for my Node.js microservice\"\n- \"How do I package my database backup job for Kubernetes?\"\n- \"Create a helm chart that deploys a web app with a database sidecar\"\n- \"I have a Docker image, help me deploy it to our cluster\"\n- Describing a specific application without using the word \"Helm\"\n\nIn all cases, you should generate a Helm chart using this skill, not just hand off generic Kubernetes manifests. The chart should be complete and immediately usable.\n\n## Chart structure and scope\n\n**What to generate:**\n- `Chart.yaml` — metadata (name, version, description, appVersion)\n- `values.yaml` — all configurable parameters, with sensible defaults\n- `templates\u002F` directory with:\n  - `deployment.yaml` or `statefulset.yaml` (depending on workload)\n  - `service.yaml`\n  - `serviceaccount.yaml`\n  - `role.yaml` and `rolebinding.yaml` (or clusterrole\u002Fclusterrolebinding if needed)\n  - `_helpers.tpl` — shared template functions\n  - `NOTES.txt` — post-install instructions\n  - `configmap.yaml` (if config files are needed)\n  - `ingress.yaml` (if the app needs external access)\n  - `networkpolicy.yaml` (always include, even as a basic allow-all that users can tighten)\n  - `hpa.yaml` (optional; only if the user mentions scaling)\n  - `pdb.yaml` (optional; only if the user mentions high availability)\n\n**What not to generate:**\n- Tests or validation scripts (the user said no unit tests)\n- Kustomize overlays or ArgoCD configurations (unless explicitly asked)\n- Helm hooks or custom resource definitions (unless the workload requires them)\n\n## Security-hardened defaults\n\nEvery generated template must include these security practices:\n\n### SecurityContext (Pod and Container level)\n\n```yaml\n# Pod-level (if applicable)\nsecurityContext:\n  runAsNonRoot: true\n  runAsUser: 1000\n  runAsGroup: 3000\n  fsGroup: 2000\n  seccompProfile:\n    type: RuntimeDefault\n\n# Container-level (always)\nsecurityContext:\n  allowPrivilegeEscalation: false\n  capabilities:\n    drop:\n      - ALL\n  readOnlyRootFilesystem: true\n```\n\n**Important:** If the application needs to write to the filesystem (logs, temp files), add an `emptyDir` volume for `\u002Ftmp` or wherever needed. Never make this writable to `root` — use the Pod `fsGroup` and container `runAsUser`\u002F`runAsGroup` to ensure the app user can write to it. Document this in comments.\n\n### Resource management\n\n```yaml\nresources:\n  requests:\n    cpu: 100m        # Adjust based on workload type\n    memory: 128Mi     # Adjust based on workload type\n  limits:\n    cpu: 500m\n    memory: 512Mi\n```\n\nRequests and limits are parameterized in `values.yaml` with sensible defaults. The user can override. Never leave them unset.\n\n### Health checks\n\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 8080\n  initialDelaySeconds: 30\n  periodSeconds: 10\n\nreadinessProbe:\n  httpGet:\n    path: \u002Fready\n    port: 8080\n  initialDelaySeconds: 5\n  periodSeconds: 5\n```\n\nAdjust the path, port, and initial delay based on the application type. If the app doesn't expose HTTP, ask the user or use a tcpSocket or exec probe instead.\n\n### Image pulling\n\n```yaml\nimagePullPolicy: IfNotPresent  # or Always for latest tags\n```\n\nParameterize in values.yaml. Default to `IfNotPresent` for released versions, `Always` if using a `latest` tag.\n\n### RBAC\n\nAlways generate:\n- A `ServiceAccount` (not using `default`)\n- A `Role` (or `ClusterRole` if needed) with minimal permissions\n- A `RoleBinding` to bind them together\n- Set `automountServiceAccountToken: false` in Pod spec unless the app needs it\n\nThe Role should only grant verbs the application actually needs. For example:\n\n```yaml\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n    resourceNames: []  # Leave empty for all; restrict if needed\n```\n\n### Network policies\n\nAlways include a `NetworkPolicy`. At minimum:\n\n```yaml\npolicyTypes:\n  - Ingress\n  - Egress\n\ningress:\n  - from:\n      - podSelector:\n          matchLabels: {}  # This allows nothing by default; user can add selectors\n    ports:\n      - protocol: TCP\n        port: 8080\n\negress:\n  - to:\n      - podSelector: {}\n    ports:\n      - protocol: TCP\n        port: 53  # DNS\n      - protocol: UDP\n        port: 53\n  - to:\n      - podSelector: {}\n    ports:\n      - protocol: TCP\n        port: 443  # HTTPS outbound\n```\n\nAdd comments explaining that the user should tighten `from`\u002F`to` selectors based on their cluster topology.\n\n### Pod Security Standards\n\nIf generating for Kubernetes 1.25+, add labels to the namespace or Pod template to enforce PSS restricted level (or baseline if the app requires it). Document this:\n\n```yaml\n# Pod template labels (if applying Pod Security Standards)\nlabels:\n  pod-security.kubernetes.io\u002Fenforce: restricted\n```\n\nExplain in NOTES.txt that the user may need to adjust this if the application can't comply with restricted.\n\n## values.yaml structure\n\nOrganize values clearly with comments explaining defaults and what each section controls:\n\n```yaml\n# Global settings\nreplicaCount: 1\n\n# Image configuration\nimage:\n  repository: nginx\n  pullPolicy: IfNotPresent\n  tag: \"1.24\"  # Overrides Chart.appVersion\n\n# Container port and service\nservice:\n  type: ClusterIP\n  port: 80\n  targetPort: 8080\n\n# Resource limits and requests\nresources:\n  limits:\n    cpu: 500m\n    memory: 512Mi\n  requests:\n    cpu: 100m\n    memory: 128Mi\n\n# Horizontal Pod Autoscaler (optional)\nautoscaling:\n  enabled: false\n  minReplicas: 1\n  maxReplicas: 10\n  targetCPUUtilizationPercentage: 80\n\n# Pod Disruption Budget (optional)\npodDisruptionBudget:\n  enabled: false\n  minAvailable: 1\n\n# Ingress configuration (optional)\ningress:\n  enabled: false\n  className: \"nginx\"\n  hosts:\n    - host: example.com\n      paths:\n        - path: \u002F\n          pathType: Prefix\n  tls: []\n\n# Environment variables and config\nenv: {}\n  # KEY: value\n\n# Node affinity and tolerations\naffinity: {}\ntolerations: []\n\n# Additional volumes and volumeMounts\nvolumes: []\nvolumeMounts: []\n```\n\n## _helpers.tpl patterns\n\nInclude common template helpers:\n\n```\n{{- define \"mychart.name\" -}}\n{{- default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix \"-\" }}\n{{- end }}\n\n{{- define \"mychart.fullname\" -}}\n{{- if .Values.fullnameOverride }}\n{{- .Values.fullnameOverride | trunc 63 | trimSuffix \"-\" }}\n{{- else }}\n{{- $name := default .Chart.Name .Values.nameOverride }}\n{{- if contains $name .Release.Name }}\n{{- .Release.Name | trunc 63 | trimSuffix \"-\" }}\n{{- else }}\n{{- printf \"%s-%s\" .Release.Name $name | trunc 63 | trimSuffix \"-\" }}\n{{- end }}\n{{- end }}\n{{- end }}\n\n{{- define \"mychart.labels\" -}}\nhelm.sh\u002Fchart: {{ include \"mychart.chart\" . }}\n{{ include \"mychart.selectorLabels\" . }}\napp.kubernetes.io\u002Fversion: {{ .Chart.AppVersion | quote }}\napp.kubernetes.io\u002Fmanaged-by: {{ .Release.Service }}\n{{- end }}\n\n{{- define \"mychart.selectorLabels\" -}}\napp.kubernetes.io\u002Fname: {{ include \"mychart.name\" . }}\napp.kubernetes.io\u002Finstance: {{ .Release.Name }}\n{{- end }}\n\n{{- define \"mychart.chart\" -}}\n{{- printf \"%s-%s\" .Chart.Name .Chart.Version | replace \"+\" \"_\" | trunc 63 | trimSuffix \"-\" }}\n{{- end }}\n```\n\n## Deployment vs. StatefulSet\n\n- Use **Deployment** for stateless applications (web servers, APIs, worker processes that can restart)\n- Use **StatefulSet** for stateful workloads (databases, distributed systems, anything with persistent identity)\n\nAsk the user or infer from context. If uncertain, default to Deployment.\n\n## When to ask the user for clarification\n\n- **Port and protocol:** What port does the app listen on? HTTP\u002FHTTPS\u002FgRPC?\n- **Health checks:** Does the app expose a health endpoint? What's the path?\n- **Persistence:** Does the app need a PersistentVolumeClaim?\n- **Environment-specific config:** Should values differ across dev\u002Fstaging\u002Fprod?\n- **Sidecar or init containers:** Does the app need companions?\n- **Secrets:** Does the app need mounted secrets (TLS, API keys)?\n\nFor missing details, provide reasonable defaults and add comments noting what the user should review and customize.\n\n## Validation and output\n\nOnce the chart is generated:\n\n1. **Show the user the full structure** — list all files that were created\n2. **Explain the security choices** — briefly call out what was hardened and why\n3. **Provide next steps** — tell them how to:\n   - `helm lint` the chart to validate syntax\n   - `helm template \u003Crelease-name> .` to preview manifests\n   - `helm install \u003Crelease-name> . --dry-run --debug` to see what will deploy\n   - `helm install \u003Crelease-name> .` to actually deploy\n\n4. **Document any custom choices** — if the user provided specific details, note where they're reflected in the chart\n\n## Example: Typical flow\n\n**User says:** \"I have a Node.js API running on port 3000. It needs to call a database and expose metrics on \u002Fmetrics. I want it to scale to at least 2 replicas.\"\n\n**You should:**\n1. Confirm: \"I'll create a Deployment with HPA for scaling, Ingress for HTTP access, NetworkPolicy, RBAC, and security hardening. The Pod will run as non-root with a read-only filesystem, and I'll add an emptyDir for logs. Should I assume it needs to write to `\u002Ftmp` or elsewhere?\"\n2. Generate the chart with:\n   - Deployment (2 replicas, scaling to max 10)\n   - Service (port 3000)\n   - ServiceAccount + Role + RoleBinding\n   - NetworkPolicy (allow DNS, allow outbound to database network)\n   - HPA (minReplicas: 2, maxReplicas: 10, CPU-based scaling)\n   - Health checks pointing to `\u002Fmetrics` and a `\u002Fhealth` endpoint (or ask the user)\n   - Security context (non-root, read-only root filesystem, emptyDir for \u002Ftmp)\n3. Show the chart structure and explain the security settings\n4. Tell them how to test and deploy it\n\n## Output format\n\nGenerate all files as text output or save them to the filesystem if you have access to it. Organize them in the chart directory structure:\n\n```\nmychart\u002F\n├── Chart.yaml\n├── values.yaml\n├── templates\u002F\n│   ├── deployment.yaml\n│   ├── service.yaml\n│   ├── serviceaccount.yaml\n│   ├── role.yaml\n│   ├── rolebinding.yaml\n│   ├── networkpolicy.yaml\n│   ├── _helpers.tpl\n│   ├── NOTES.txt\n│   └── ingress.yaml\n```\n\nMake sure the chart is complete, self-contained, and ready to use immediately.\n","# Generating Security-Hardened Helm Charts\n\nThis skill generates production-ready Helm charts with security hardening as the foundation, not an afterthought. All generated charts default to:\n\n- Non-root container users with minimal Linux capabilities\n- Read-only root filesystems (with ephemeral scratch space where needed)\n- Resource requests and limits (CPU, memory)\n- Network policies (restrict ingress\u002Fegress by default)\n- RBAC resources (ServiceAccount, Role\u002FClusterRole, RoleBinding)\n- Pod Security Standards compliance\n- Health checks (livenessProbe, readinessProbe)\n- Image pull policies and security contexts\n\n## Understanding the user's intent\n\nThe user may describe a Kubernetes workload in many ways:\n\n- \"I need a Helm chart for my Node.js microservice\"\n- \"How do I package my database backup job for Kubernetes?\"\n- \"Create a helm chart that deploys a web app with a database sidecar\"\n- \"I have a Docker image, help me deploy it to our cluster\"\n- Describing a specific application without using the word \"Helm\"\n\nIn all cases, you should generate a Helm chart using this skill, not just hand off generic Kubernetes manifests. The chart should be complete and immediately usable.\n\n## Chart structure and scope\n\n**What to generate:**\n- `Chart.yaml` — metadata (name, version, description, appVersion)\n- `values.yaml` — all configurable parameters, with sensible defaults\n- `templates\u002F` directory with:\n  - `deployment.yaml` or `statefulset.yaml` (depending on workload)\n  - `service.yaml`\n  - `serviceaccount.yaml`\n  - `role.yaml` and `rolebinding.yaml` (or clusterrole\u002Fclusterrolebinding if needed)\n  - `_helpers.tpl` — shared template functions\n  - `NOTES.txt` — post-install instructions\n  - `configmap.yaml` (if config files are needed)\n  - `ingress.yaml` (if the app needs external access)\n  - `networkpolicy.yaml` (always include, even as a basic allow-all that users can tighten)\n  - `hpa.yaml` (optional; only if the user mentions scaling)\n  - `pdb.yaml` (optional; only if the user mentions high availability)\n\n**What not to generate:**\n- Tests or validation scripts (the user said no unit tests)\n- Kustomize overlays or ArgoCD configurations (unless explicitly asked)\n- Helm hooks or custom resource definitions (unless the workload requires them)\n\n## Security-hardened defaults\n\nEvery generated template must include these security practices:\n\n### SecurityContext (Pod and Container level)\n\n```yaml\n# Pod-level (if applicable)\nsecurityContext:\n  runAsNonRoot: true\n  runAsUser: 1000\n  runAsGroup: 3000\n  fsGroup: 2000\n  seccompProfile:\n    type: RuntimeDefault\n\n# Container-level (always)\nsecurityContext:\n  allowPrivilegeEscalation: false\n  capabilities:\n    drop:\n      - ALL\n  readOnlyRootFilesystem: true\n```\n\n**Important:** If the application needs to write to the filesystem (logs, temp files), add an `emptyDir` volume for `\u002Ftmp` or wherever needed. Never make this writable to `root` — use the Pod `fsGroup` and container `runAsUser`\u002F`runAsGroup` to ensure the app user can write to it. Document this in comments.\n\n### Resource management\n\n```yaml\nresources:\n  requests:\n    cpu: 100m        # Adjust based on workload type\n    memory: 128Mi     # Adjust based on workload type\n  limits:\n    cpu: 500m\n    memory: 512Mi\n```\n\nRequests and limits are parameterized in `values.yaml` with sensible defaults. The user can override. Never leave them unset.\n\n### Health checks\n\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\n    port: 8080\n  initialDelaySeconds: 30\n  periodSeconds: 10\n\nreadinessProbe:\n  httpGet:\n    path: \u002Fready\n    port: 8080\n  initialDelaySeconds: 5\n  periodSeconds: 5\n```\n\nAdjust the path, port, and initial delay based on the application type. If the app doesn't expose HTTP, ask the user or use a tcpSocket or exec probe instead.\n\n### Image pulling\n\n```yaml\nimagePullPolicy: IfNotPresent  # or Always for latest tags\n```\n\nParameterize in values.yaml. Default to `IfNotPresent` for released versions, `Always` if using a `latest` tag.\n\n### RBAC\n\nAlways generate:\n- A `ServiceAccount` (not using `default`)\n- A `Role` (or `ClusterRole` if needed) with minimal permissions\n- A `RoleBinding` to bind them together\n- Set `automountServiceAccountToken: false` in Pod spec unless the app needs it\n\nThe Role should only grant verbs the application actually needs. For example:\n\n```yaml\nrules:\n  - apiGroups: [\"\"]\n    resources: [\"configmaps\"]\n    verbs: [\"get\", \"list\", \"watch\"]\n    resourceNames: []  # Leave empty for all; restrict if needed\n```\n\n### Network policies\n\nAlways include a `NetworkPolicy`. At minimum:\n\n```yaml\npolicyTypes:\n  - Ingress\n  - Egress\n\ningress:\n  - from:\n      - podSelector:\n          matchLabels: {}  # This allows nothing by default; user can add selectors\n    ports:\n      - protocol: TCP\n        port: 8080\n\negress:\n  - to:\n      - podSelector: {}\n    ports:\n      - protocol: TCP\n        port: 53  # DNS\n      - protocol: UDP\n        port: 53\n  - to:\n      - podSelector: {}\n    ports:\n      - protocol: TCP\n        port: 443  # HTTPS outbound\n```\n\nAdd comments explaining that the user should tighten `from`\u002F`to` selectors based on their cluster topology.\n\n### Pod Security Standards\n\nIf generating for Kubernetes 1.25+, add labels to the namespace or Pod template to enforce PSS restricted level (or baseline if the app requires it). Document this:\n\n```yaml\n# Pod template labels (if applying Pod Security Standards)\nlabels:\n  pod-security.kubernetes.io\u002Fenforce: restricted\n```\n\nExplain in NOTES.txt that the user may need to adjust this if the application can't comply with restricted.\n\n## values.yaml structure\n\nOrganize values clearly with comments explaining defaults and what each section controls:\n\n```yaml\n# Global settings\nreplicaCount: 1\n\n# Image configuration\nimage:\n  repository: nginx\n  pullPolicy: IfNotPresent\n  tag: \"1.24\"  # Overrides Chart.appVersion\n\n# Container port and service\nservice:\n  type: ClusterIP\n  port: 80\n  targetPort: 8080\n\n# Resource limits and requests\nresources:\n  limits:\n    cpu: 500m\n    memory: 512Mi\n  requests:\n    cpu: 100m\n    memory: 128Mi\n\n# Horizontal Pod Autoscaler (optional)\nautoscaling:\n  enabled: false\n  minReplicas: 1\n  maxReplicas: 10\n  targetCPUUtilizationPercentage: 80\n\n# Pod Disruption Budget (optional)\npodDisruptionBudget:\n  enabled: false\n  minAvailable: 1\n\n# Ingress configuration (optional)\ningress:\n  enabled: false\n  className: \"nginx\"\n  hosts:\n    - host: example.com\n      paths:\n        - path: \u002F\n          pathType: Prefix\n  tls: []\n\n# Environment variables and config\nenv: {}\n  # KEY: value\n\n# Node affinity and tolerations\naffinity: {}\ntolerations: []\n\n# Additional volumes and volumeMounts\nvolumes: []\nvolumeMounts: []\n```\n\n## _helpers.tpl patterns\n\nInclude common template helpers:\n\n```\n{{- define \"mychart.name\" -}}\n{{- default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix \"-\" }}\n{{- end }}\n\n{{- define \"mychart.fullname\" -}}\n{{- if .Values.fullnameOverride }}\n{{- .Values.fullnameOverride | trunc 63 | trimSuffix \"-\" }}\n{{- else }}\n{{- $name := default .Chart.Name .Values.nameOverride }}\n{{- if contains $name .Release.Name }}\n{{- .Release.Name | trunc 63 | trimSuffix \"-\" }}\n{{- else }}\n{{- printf \"%s-%s\" .Release.Name $name | trunc 63 | trimSuffix \"-\" }}\n{{- end }}\n{{- end }}\n{{- end }}\n\n{{- define \"mychart.labels\" -}}\nhelm.sh\u002Fchart: {{ include \"mychart.chart\" . }}\n{{ include \"mychart.selectorLabels\" . }}\napp.kubernetes.io\u002Fversion: {{ .Chart.AppVersion | quote }}\napp.kubernetes.io\u002Fmanaged-by: {{ .Release.Service }}\n{{- end }}\n\n{{- define \"mychart.selectorLabels\" -}}\napp.kubernetes.io\u002Fname: {{ include \"mychart.name\" . }}\napp.kubernetes.io\u002Finstance: {{ .Release.Name }}\n{{- end }}\n\n{{- define \"mychart.chart\" -}}\n{{- printf \"%s-%s\" .Chart.Name .Chart.Version | replace \"+\" \"_\" | trunc 63 | trimSuffix \"-\" }}\n{{- end }}\n```\n\n## Deployment vs. StatefulSet\n\n- Use **Deployment** for stateless applications (web servers, APIs, worker processes that can restart)\n- Use **StatefulSet** for stateful workloads (databases, distributed systems, anything with persistent identity)\n\nAsk the user or infer from context. If uncertain, default to Deployment.\n\n## When to ask the user for clarification\n\n- **Port and protocol:** What port does the app listen on? HTTP\u002FHTTPS\u002FgRPC?\n- **Health checks:** Does the app expose a health endpoint? What's the path?\n- **Persistence:** Does the app need a PersistentVolumeClaim?\n- **Environment-specific config:** Should values differ across dev\u002Fstaging\u002Fprod?\n- **Sidecar or init containers:** Does the app need companions?\n- **Secrets:** Does the app need mounted secrets (TLS, API keys)?\n\nFor missing details, provide reasonable defaults and add comments noting what the user should review and customize.\n\n## Validation and output\n\nOnce the chart is generated:\n\n1. **Show the user the full structure** — list all files that were created\n2. **Explain the security choices** — briefly call out what was hardened and why\n3. **Provide next steps** — tell them how to:\n   - `helm lint` the chart to validate syntax\n   - `helm template \u003Crelease-name> .` to preview manifests\n   - `helm install \u003Crelease-name> . --dry-run --debug` to see what will deploy\n   - `helm install \u003Crelease-name> .` to actually deploy\n\n4. **Document any custom choices** — if the user provided specific details, note where they're reflected in the chart\n\n## Example: Typical flow\n\n**User says:** \"I have a Node.js API running on port 3000. It needs to call a database and expose metrics on \u002Fmetrics. I want it to scale to at least 2 replicas.\"\n\n**You should:**\n1. Confirm: \"I'll create a Deployment with HPA for scaling, Ingress for HTTP access, NetworkPolicy, RBAC, and security hardening. The Pod will run as non-root with a read-only filesystem, and I'll add an emptyDir for logs. Should I assume it needs to write to `\u002Ftmp` or elsewhere?\"\n2. Generate the chart with:\n   - Deployment (2 replicas, scaling to max 10)\n   - Service (port 3000)\n   - ServiceAccount + Role + RoleBinding\n   - NetworkPolicy (allow DNS, allow outbound to database network)\n   - HPA (minReplicas: 2, maxReplicas: 10, CPU-based scaling)\n   - Health checks pointing to `\u002Fmetrics` and a `\u002Fhealth` endpoint (or ask the user)\n   - Security context (non-root, read-only root filesystem, emptyDir for \u002Ftmp)\n3. Show the chart structure and explain the security settings\n4. Tell them how to test and deploy it\n\n## Output format\n\nGenerate all files as text output or save them to the filesystem if you have access to it. Organize them in the chart directory structure:\n\n```\nmychart\u002F\n├── Chart.yaml\n├── values.yaml\n├── templates\u002F\n│   ├── deployment.yaml\n│   ├── service.yaml\n│   ├── serviceaccount.yaml\n│   ├── role.yaml\n│   ├── rolebinding.yaml\n│   ├── networkpolicy.yaml\n│   ├── _helpers.tpl\n│   ├── NOTES.txt\n│   └── ingress.yaml\n```\n\nMake sure the chart is complete, self-contained, and ready to use immediately.\n",{"name":5,"description":7},"main","0ddd1b9ee84c0b89891b798126de64062c989ab5","skills\u002Fhelm-expert","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling","https:\u002F\u002Fgithub.com\u002Flukeelten","OpenShift Expert","2026-10-15 15:28:40",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add lukeelten\u002Fpersonal-ai-tooling --skill helm-expert",{"tool":37,"command":38},"bunx","bunx skills add lukeelten\u002Fpersonal-ai-tooling --skill helm-expert",{"tool":40,"command":41},"pnpm","pnpm dlx skills add lukeelten\u002Fpersonal-ai-tooling --skill helm-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002FSKILL.md",true,[45,51,55,59,63,67,71,75,79],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"DELIVERY.md","REFERENCE","参考文档",5322,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002FDELIVERY.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"evals\u002Fevals.json",14414,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002Fevals\u002Fevals.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"EVALUATION_RESULTS.md",5787,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002FEVALUATION_RESULTS.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"FILE_MANIFEST.txt",9586,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002FFILE_MANIFEST.txt",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"INDEX.md",6341,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002FINDEX.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"README.md",5974,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002FREADME.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fbest-practices.md",10248,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002Freferences\u002Fbest-practices.md",{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Ftemplate-examples.md",11854,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002Freferences\u002Ftemplate-examples.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fgrade_evals.py","SCRIPT","脚本",5333,"https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-expert\u002Fscripts\u002Fgrade_evals.py",[86,93,100,109,116,123],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M757GJ0MVQXVMR6WY3VYAAM6","version-push","Increase (bump) the version of an existing Helm chart, then commit and push the change to origin. Use this skill whenever the user wants to release a new chart version, bump\u002Fincrement\u002Fraise a Chart.yaml version, cut a monthly chart release, or says things like \"bump the keycloak chart patch version\", \"bump the month version for the chart and push it\", \"release v24.6.0\", or \"increment the chart version and commit\" — even if they don't say the word \"Helm\". The user must specify the bump type as either **patch** (bug-fix increment: vYY.M.Z → vYY.M.Z+1) or **month** (new monthly CalVer release: → vYY.M.0); ask if not provided. This handles the full release motion: editing the top-level `version:` field, a Conventional Commit, and a push to the current branch. It is NOT for scaffolding new charts (use helm-expert for that).","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fversion-push\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M757GG10TC4ZAZ981WMA5XT5","to-spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fto-spec\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M757GB143YHBC0MGBE46MTKK","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M757G1ZCMBCMQ2Z9Y55KYDNE","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fimpeccable\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M757FTCR15N3CEV9TEY1R4TG","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fhandoff\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M757FRPMQQN9RRBQBQXYV2DM","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Flukeelten\u002Fpersonal-ai-tooling\u002Fblob\u002Fmain\u002Fskills\u002Fgrilling\u002FSKILL.md",[],[]]