Can this skill validate playbooks before execution?

Yes, it includes patterns for 'pre-flight' tasks using the ansible.builtin.assert module to verify required variables and system requirements before making changes.

When should I use include_tasks versus import_tasks?

Use import_tasks for static, parse-time inclusion where order is fixed. Use include_tasks for dynamic, runtime evaluation, which is required for loops or tasks based on host facts.

How does this skill help with variable management?

It provides a clear organizational structure for inventory variables (group_vars and host_vars) and enforces a naming convention that respects Ansible's 22 levels of variable precedence.

What is a state-based playbook pattern?

It is a design pattern where a single playbook handles both resource creation and removal by mapping a 'state' variable (typically present or absent) directly to Ansible modules.

Ansible Playbook Architect

Name: Ansible Playbook Architect
Author: basher83

bybasher83

•

Despliegue y DevOps

Designs structured, maintainable, and state-based Ansible playbooks following industry best practices.

Acerca de

The Ansible Playbook Architect skill empowers Claude to create professional-grade infrastructure automation by providing standardized patterns for playbook design. It focuses on implementing idempotent, state-based patterns (present/absent), organizing complex play structures with pre and post tasks, and managing variable precedence across global, group, and host scopes. Whether you are scaffolding a new project or refactoring monolithic scripts, this skill ensures your playbooks are modular, scalable, and follow community-standard conventions for variables and handler management.

Características Principales

Standardized play structure and task organization
Automated pre-flight validation and assertion logic
Dynamic vs. static task inclusion strategies
Advanced variable scoping and precedence mapping
State-based playbook design (present/absent patterns)
5 GitHub stars

Casos de Uso

Implementing multi-stage cluster initialization and deployment workflows
Refactoring large, complex playbooks into modular task files
Scaffolding new enterprise infrastructure-as-code projects

Acerca de

Características Principales

Standardized play structure and task organization
Automated pre-flight validation and assertion logic
Dynamic vs. static task inclusion strategies
Advanced variable scoping and precedence mapping
State-based playbook design (present/absent patterns)
5 GitHub stars

Casos de Uso

Implementing multi-stage cluster initialization and deployment workflows
Refactoring large, complex playbooks into modular task files
Scaffolding new enterprise infrastructure-as-code projects