Skip to main content

Lang Ansible

Lint and syntax-check Ansible playbooks.

Skill metadata​

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

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.

Ansible Language Pack Skill

Drive Ansible 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-playbooks, Ansible приводит машины к нему.

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

  • настройка серверов
  • идемпотентные playbooks
  • роли и inventories
  • конфиг-менеджмент без агентов

When to Use​

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

  • есть ansible.cfg / galaxy.yml / requirements.yml
  • нужно настроить VPS/серверы
  • пользователь просит Ansible

Manifests (автодетект репозитория): ansible.cfg, ansible.cfg.ini, galaxy.yml, requirements.yml

Обычно рядом: Часто Terraform (создать машину) + Ansible (настроить); Docker на хостах.

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

When NOT to use​

  • облачные ресурсы (VM/сеть/БД) как код → Terraform
  • контейнеры приложения → Docker
  • K8s workloads → yaml/kustomize/helm

Prerequisites​

vibeos pack apply lang-ansible --apply
vibeos pack apply project-intelligence --apply

How to Run​

vibeos project index build
ansible-lint
ansible-playbook --syntax-check site.yml || true

Quick Reference​

GoalCommand
Apply packvibeos pack apply lang-ansible --apply
Doctorvibeos language doctor ansible
Primary testansible-lint
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​

  • Prefer --check / syntax-check before applying to real hosts.
  • Never commit vault passwords; use ansible-vault.
  • Do not invent core tools; stay on terminal + read_file + index CLI.

Verification​

vibeos language doctor ansible
vibeos project index status