Skip to content
TrustedSkillsbeta
Back to all skills

Helm Validator

Listed
akin-ozer·vlatest·cloud·Apache-2.0

The Helm Validator ensures your Helm charts are syntactically correct and follow best practices, preventing deployment errors and improving chart quality.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add akin-ozer/cc-devops-skills --skill helm-validator -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

akin-ozer

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: helm.sh, kubernetes.io.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    raw.githubusercontent.comsource hosthelm.shundeclaredgithub.comsource hostkubernetes.ioundeclared

    What it found

    • devops-skills-plugin/skills/helm-validator/scripts/setup_tools.sh:100contacts helm.sh
      echo "  Manual:   https://helm.sh/docs/intro/install/"
    • devops-skills-plugin/skills/helm-validator/scripts/setup_tools.sh:132contacts kubernetes.io
      echo "  Linux:    https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/"

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 1 place.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • devops-skills-plugin/skills/helm-validator/scripts/setup_tools.sh:98remote script piped into a shell
      echo "  Linux:    curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash"

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • Pinned to a commit: passed

    Scanned akin-ozer/cc-devops-skills at 276af751e6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
276af751e6
Manifest
devops-skills-plugin/skills/helm-validator/SKILL.md
Scanned
24 files, 5,417 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The helm-validator skill validates Helm charts against defined schemas and best practices. It ensures that your Kubernetes manifests are correctly formatted, contain necessary fields, and adhere to established standards. This helps prevent deployment errors and promotes consistency across environments.

When to use it

  • Pre-deployment checks: Validate a Helm chart before deploying it to a staging or production environment.
  • CI/CD pipelines: Integrate validation into your continuous integration and delivery process to automatically check charts on every commit.
  • Chart maintenance: Regularly validate existing charts to ensure they remain compliant with evolving standards.
  • Team onboarding: Ensure new team members are deploying valid Helm charts by enforcing schema checks.

Key capabilities

  • Helm chart validation
  • Schema enforcement
  • Best practices adherence

Example prompts

  • "Validate this Helm chart: /path/to/my/chart."
  • "Run the validator against my current working directory's Helm chart."
  • "Check if this Helm chart is compliant with the latest Kubernetes standards."

Tips & gotchas

The skill requires Helm to be installed and configured on your system. Ensure you have appropriate permissions to access and validate the specified charts.