leogallego/claude-ansible-skills

Answer Ansible questions and review Ansible code using official documentation. Use when the user asks about Ansible concepts, syntax, best practices, deprecations, or wants Ansible code reviewed against official docs. Use when user says "check my playbook against docs", "what does Ansible say about X", "how do I use module Y", or "review my role". Do NOT use for CoP good practices review (use ansible-good-practices instead). Do NOT use for general Python or YAML questions unrelated to Ansible.

Review Ansible code against Red Hat CoP automation good practices. Use when the user wants to audit, lint, review, check, or validate Ansible roles, playbooks, collections, or inventory for compliance with CoP rules. Use when user says "lint my role", "check my playbook", "review best practices", or "audit my Ansible code". Do NOT use for general Python or YAML linting unrelated to Ansible.

Scaffold a new Ansible content collection following all Red Hat CoP good practices. Use when the user wants to create, generate, or bootstrap a new Ansible collection. Use when user says "create a collection", "new collection", "scaffold collection", or "init collection". Leverages ansible-creator when available. Do NOT use for reviewing existing collections (use ansible-good-practices instead).

Scaffold a new Ansible execution environment project following good practices. Use when the user wants to create, generate, or bootstrap a new EE. Use when user says "create an EE", "new execution environment", "scaffold EE", or "build EE project". Leverages ansible-creator when available. Do NOT use for building existing EEs or managing containers.

Scaffold a new Ansible role following all Red Hat CoP good practices. Use when the user wants to create, generate, or bootstrap a new Ansible role. Use when user says "create a role", "new role", "scaffold role", or "generate role skeleton". Leverages ansible-creator when available. Do NOT use for reviewing existing roles (use ansible-good-practices instead).

Display the Zen of Ansible principles and review Ansible code against them. Use when the user wants to see the Zen of Ansible, get philosophical guidance on their automation approach, or review code for simplicity, readability, and clarity. Use when user says "zen of ansible", "simplify my playbook", "is this too complex", or "clean code review". Do NOT use for strict rule compliance (use ansible-good-practices instead).