helm-validator_skill

This skill validates, lints, and analyzes Helm charts and rendered resources to detect issues, ensuring best practices without modifying source files.
  • HCL

83

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill akin-ozer/cc-devops-skills --skill helm-validator

  • .gitignore304 B
  • SKILL.md30.5 KB

Overview

This skill is a comprehensive Helm chart validator and analysis toolkit that inspects chart structure, renders templates, validates YAML and schemas, detects CRDs and looks up CRD docs, and enforces security best practices. It is read-only: it identifies issues, proposes concrete fixes, and lists automation opportunities without modifying files. Use it to catch template, schema, and security problems before packaging or deploying charts.

How this skill works

The skill runs a staged workflow: tool presence checks, chart structure validation, helm linting, template rendering, yamllint checks, CRD detection and documentation lookup, schema validation with kubeconform, optional cluster dry-run, and a mandatory security scan. It aggregates findings into a final validation report that categorizes errors, warnings, and informational recommendations, and proposes precise file-level fixes and automation steps for the user to apply.

When to use it

  • Before packaging or releasing a Helm chart
  • When debugging template rendering or lint errors
  • When testing charts with alternative values or upgrades
  • When the chart includes CRDs or needs CRD spec lookup
  • To enforce Kubernetes and security best practices before deployment
  • When automating chart refactors or helper templates

Best practices

  • Run tool check first and install missing tooling before validation
  • Keep values.schema.json to validate user inputs and catch type errors early
  • Render templates with representative values, including edge cases and upgrade scenarios
  • Treat kubeconform schema errors as high priority; use CRD docs for custom resources
  • Ensure every Pod/Container has securityContext, resource requests/limits, and probes
  • Always produce a final summary with categorized issues and proposed fixes (read-only)

Example use cases

  • Validate a CI pipeline step that lints and renders charts before packaging
  • Investigate a template rendering failure caused by undefined values or incorrect template functions
  • Audit a chart that ships CRDs by extracting required CRD fields from upstream documentation
  • Perform a pre-deploy security audit checking for missing securityContext, resource limits, or :latest images
  • Refactor templates into _helpers.tpl and verify no behavioral regressions with helm template

FAQ

No. This is a read-only validator. It only analyzes files and proposes changes; any edits must be applied manually or with a separate generator tool.

How does CRD documentation lookup work?

The skill first attempts a library lookup (preferred) for CRD docs, then falls back to targeted web search. It extracts required spec fields, types, examples, and version-specific notes to validate CRD instances.

Can I run cluster-side dry-runs?

Yes if kubectl is configured and cluster access exists. The skill performs server-side dry-run tests to catch admission controllers, policy, and quota issues; otherwise it documents that cluster validation was skipped.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
helm-validator skill by akin-ozer/cc-devops-skills | VeilStrat