Skills Guide

Add Helm Chart

VerifiedSafe

Scaffold a new Helm chart with standard templates and default values. Helps when adding a new service to a Kubernetes deployment while following project conventions.

Sby Skills Guide Bot
DevOpsIntermediate
1406/2/2026
Claude Code
#helm#kubernetes#scaffolding#chart

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Our review

Scaffolds a new Helm chart with standard templates and project conventions under deploy/charts/.

Strengths

  • Follows project conventions via .claude/rules/helm-charts.md
  • Generates all essential templates (deployment, service, configmap, ingress, HPA)
  • Includes sensible defaults for resources and health checks
  • Validates the chart with helm lint and template commands

Limitations

  • Assumes a specific directory structure (deploy/charts/) and namespace (signalbeam)
  • Does not handle advanced Helm features like subcharts or dependencies
  • Uses static templates that may need customization for non-standard services
When to use it

Use when adding a new microservice to the Signalbeam platform and you need a standardized Kubernetes chart.

When not to use it

Do not use when creating a chart for a service outside the Signalbeam ecosystem or when you need a highly customized chart structure.

Security analysis

Safe
Quality score88/100

The skill only uses safe commands (helm lint, helm template) and writes to a designated directory. No risky operations, no execution of arbitrary code, no exfiltration.

No concerns found

Examples

Add a chart for a service
Add a Helm chart for the new user-service
Scaffold device-manager chart
Scaffold a new Helm chart named device-manager

name: add-helm-chart description: Scaffold a new Helm chart with standard templates and values allowed-tools: Bash, Write, Read, Glob user-invocable: true

Add Helm Chart

Scaffold a new Helm chart following project conventions.

Arguments

  • {chart-name} — Name of the chart (required, e.g., signalbeam-platform, device-manager)

Process

  1. Create the chart directory structure under deploy/charts/{chart-name}/:
deploy/charts/{chart-name}/
├── Chart.yaml
├── values.yaml
├── templates/
│   ├── _helpers.tpl
│   ├── deployment.yaml
│   ├── service.yaml
│   ├── configmap.yaml
│   ├── ingress.yaml
│   └── hpa.yaml

  1. Read .claude/rules/helm-charts.md for project conventions.

  2. Generate files following these conventions:

    • Namespace: signalbeam
    • Standard Kubernetes labels: app.kubernetes.io/name, app.kubernetes.io/instance, app.kubernetes.io/version
    • Health check paths: /health/live (liveness), /health/ready (readiness)
    • Resource limits and requests with sensible defaults
    • HPA with min 1, max 3 replicas

  3. Chart.yaml template:

apiVersion: v2
name: {chart-name}
description: {description}
type: application
version: 0.1.0
appVersion: "0.1.0"

  1. values.yaml — Include configurable values for:

    • image.repository, image.tag, image.pullPolicy
    • replicaCount
    • resources.requests and resources.limits
    • service.type, service.port
    • ingress.enabled, ingress.hosts
    • env (environment variables as key-value map)

  2. Validate the chart:

helm lint deploy/charts/{chart-name}
helm template test deploy/charts/{chart-name} > /dev/null

After Scaffolding

Report what was created and remind to:

  • Customize values.yaml for the specific service
  • Add environment-specific value overrides if needed
  • Update any umbrella chart dependencies if applicable
Related skills

Docker Compose Architect

DevOps

Designs optimized Docker Compose configurations.

Claude CodeCopilotadvanced
430
156
1,480
Admin

Incident Postmortem Writer

DevOps

Writes structured and blameless incident postmortem reports.

claudeCursorWindsurfintermediate
141
43
483
Admin

Runbook Creator

DevOps

Creates clear operational runbooks for common DevOps procedures.

claudeCursorWindsurfintermediate
108
32
405
Admin