k8s-yaml-validator

Validate Kubernetes YAML manifests for syntax, schema, and cluster compatibility.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/devkeni/Skills --skill k8s-yaml-validator-devkeni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-yaml-validator
Source: https://github.com/devkeni/Skills/tree/main/backend-devops/k8s-yaml-validator
Command: npx skills add https://github.com/devkeni/Skills --skill k8s-yaml-validator-devkeni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Kubernetes manifests often ship with subtle syntax, schema, or CRD issues that can cause failed deployments. This skill provides a deterministic, multi-stage validation workflow to catch these problems before applying changes.

Core Features & Use Cases

  • YAML syntax validation with yamllint for single and multi-document files, including error detection and suggested fixes.
  • CRD detection and documentation lookup to understand custom resource requirements and constraints.
  • Kubernetes schema validation with kubeconform, including strict and missing-schemas options.
  • Optional server-side or client-side dry-run checks to validate behavior without applying changes.
  • Comprehensive, read-only validation reports that guide remediation without modifying source files.

Quick Start

Validate a Kubernetes manifest file to obtain a comprehensive, read-only validation report.

Frequently Asked Questions about k8s-yaml-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Kubernetes YAML manifests before deployment?

Validate Kubernetes YAML manifests by running multi-stage checks for syntax, schema, and cluster compatibility. This workflow uses yamllint and kubeconform to generate a detailed, read-only remediation report that catches configuration issues without applying changes.

What is the best way to lint Kubernetes YAML for CRD schema issues?

Linting Kubernetes YAML for CRD schema issues involves detecting custom resources and validating them against kubeconform schemas. This ensures strict schema compliance and identifies missing schema definitions in multi-document files before deployment.

Can I run a kubectl dry-run on multi-document YAML files without applying changes?

Yes, you can run optional server-side or client-side kubectl dry-run checks on multi-document YAML files. This validates cluster behavior and compatibility safely, generating a comprehensive read-only report without modifying your source files.

Does this YAML validation workflow support CI/CD deployment pipelines?

Yes, this YAML validation workflow supports CI/CD deployment pipelines. It applies deterministic validation to single and multi-document files in development, CI, and production contexts to prevent faulty Kubernetes configurations from reaching deployment.

Why does my Kubernetes deployment fail due to YAML syntax errors?

Kubernetes deployments often fail due to subtle YAML syntax or schema issues. Using yamllint for syntax validation and kubeconform for schema checks catches these errors early and provides suggested fixes in a read-only remediation report.