Skip to main content

Lang Yaml

Lint and validate YAML, Helm, and Kustomize.

Skill metadata​

SourceBundled (installed by default)
Pathskills/software-development/lang-yaml
Version1.0.0
AuthorVibeOS
LicenseMIT
Platformslinux, macos, windows

Reference: full SKILL.md​

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

YAML / K8s / CI Language Pack Skill

Drive YAML / K8s / CI work with the project index and standard CLI recipes. LSP hint: yaml-language-server (editor-side when applicable). Zero new core tools.

What this language is (beginner)​

Формат конфигов, а не язык приложения. Через YAML описывают Kubernetes, Helm, GitHub Actions и кучу DevOps-настроек.

Лучше всего для:

  • Kubernetes manifests
  • Helm charts
  • GitHub Actions workflows
  • общие YAML-конфиги с yamllint

When to Use​

Выбирай этот pack, если:

  • есть kustomization.yaml / Chart.yaml / .yamllint
  • нужно править K8s/Helm/CI YAML
  • пользователь просит kubernetes/k8s/actions

Manifests (автодетект репозитория): .yamllint, .yamllint.yml, .yamllint.yaml, kustomization.yaml, Chart.yaml, skaffold.yaml

Обычно рядом: Docker images; Terraform для облака; любой app-язык.

См. также skill choose-language-pack и vibeos language recommend "…".

When NOT to use​

  • логика приложения → TypeScript/Go/Python/…
  • облачные ресурсы как код → Terraform
  • playbooks серверов → Ansible

Prerequisites​

vibeos pack apply lang-yaml --apply
vibeos pack apply project-intelligence --apply

How to Run​

vibeos project index build
yamllint .
kubectl kustomize . || true
helm lint . || true

Quick Reference​

GoalCommand
Apply packvibeos pack apply lang-yaml --apply
Doctorvibeos language doctor yaml
Primary testyamllint .
Choose guideskill choose-language-pack
Recommendvibeos language recommend "…"

Procedure​

  1. Для нового продукта сначала choose-language-pack / vibeos language recommend.
  2. Work from the project root that matches pack manifests.
  3. Validate (lint/config/syntax) before any apply/up/push that touches real infra.
  4. Prefer project-local tooling already present in the repo.
  5. Explain risky ops (apply, up, push) and wait for explicit user ask.

Pitfalls​

  • Validate before apply; never kubectl apply without explicit ask.
  • Keep secrets out of committed YAML (use sealed-secrets / external secrets).
  • Do not invent core tools; stay on terminal + read_file + index CLI.

Verification​

vibeos language doctor yaml
vibeos project index status