By leogallego
Create a new Ansible content collection following all Red Hat CoP good practices. Optionally uses ansible-know MCP tools to discover existing collections on Galaxy and inspect reference collections before scaffolding. 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).
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A collection of Claude Code skills for Ansible automation development following Red Hat Communities of Practice (CoP) good practices.
Review Ansible code against Red Hat CoP automation good practices loaded from per-section AsciiDoc references.
Create a new Ansible role fully compliant with CoP rules.
install.yml, configure.yml, service.yml with sub-task name prefixesansible-creator inside collections, manual creation otherwiseansible-creator is not installedCreate a new Ansible content collection using ansible-creator, then customize for full CoP compliance.
antsibull-changelogansible-creator is not installedCreate a new Ansible execution environment project using ansible-creator.
requirements.yml, requirements.txt, and bindep.txt for non-trivial EEsansible-creator is not installedAnswer Ansible questions and review code against official Ansible ecosystem documentation.
ansible-know MCP server (v0.7.0+) — install with uvx ansible-know-mcpDisplay the Zen of Ansible and review code against its 20 principles.
Each top-level ansible-* directory is a standalone Claude Code plugin with:
ansible-good-practices/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (name, version, description)
└── skills/
└── ansible-good-practices/
└── SKILL.md # Skill prompt definition
The root .claude-plugin/marketplace.json indexes all plugins for marketplace discovery.
Register the marketplace and install skills as plugins:
/plugin marketplace add https://github.com/leogallego/claude-ansible-skills
/plugin install ansible-good-practices
/plugin install ansible-new-role
/plugin install ansible-new-collection
/plugin install ansible-new-ee
/plugin install ansible-zen
Alternatively, clone and symlink individual skill directories. Each skill lives inside <plugin>/skills/<skill-name>/.
Project-level (single project):
git clone https://github.com/leogallego/claude-ansible-skills.git
cd ~/my-ansible-project
mkdir -p .claude/skills
ln -s ~/claude-ansible-skills/ansible-good-practices/skills/ansible-good-practices .claude/skills/ansible-good-practices
Profile-level (all projects):
mkdir -p ~/.claude/skills
ln -s ~/claude-ansible-skills/ansible-new-role/skills/ansible-new-role ~/.claude/skills/ansible-new-role
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub p/leogallego-ansible-new-collection-ansible-new-collectionCreate a new Ansible execution environment project following good practices. Optionally uses ansible-know MCP tools to validate collection dependencies on Galaxy and pin latest versions. 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. Do NOT use for reviewing existing EEs (use ansible-good-practices instead).
Create 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". Optionally uses ansible-know MCP tools for module-aware task generation with verified parameters. Falls back to template-based generation when MCP is unavailable. Leverages ansible-creator when available. Do NOT use for reviewing existing roles (use ansible-good-practices instead). Do NOT use for creating collections (use ansible-new-collection) or adding molecule tests to existing roles (use ansible-new-molecule).
Scaffold molecule testing for an Ansible role or collection following the current molecule testing philosophy (Ansible-native everything). Use when the user wants to add molecule tests, create test scenarios, or set up molecule for an existing role or collection. Use when user says "add molecule", "create molecule tests", "scaffold testing", "add test scenarios", or "set up molecule". Generates modern ansible-native molecule.yml (no driver/provisioner/verifier/platforms blocks), working create.yml/destroy.yml playbooks, smart verify.yml from role introspection, and optional GitHub Actions CI. Optionally uses ansible-know MCP server for module return value lookup. Do NOT use for migrating existing molecule setups (migration skill planned for a future release).
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). Do NOT use for Ansible module reference or documentation lookups (use ansible-docs instead).
Answer Ansible questions and review Ansible code using official documentation from the Ansible ecosystem. Covers ansible-core, ansible-lint, ansible-navigator, ansible-builder, ansible-creator, and molecule. 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.
Create 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". Optionally uses ansible-know MCP tools for module-aware task generation with verified parameters. Falls back to template-based generation when MCP is unavailable. Leverages ansible-creator when available. Do NOT use for reviewing existing roles (use ansible-good-practices instead). Do NOT use for creating collections (use ansible-new-collection) or adding molecule tests to existing roles (use ansible-new-molecule).
Ansible automation toolkit for playbook design, role creation, and inventory management. Includes playbook architect agent for strategic automation decisions.
Create Ansible playbooks for configuration management
Ansible playbook validation and configuration management best practices
End-to-end Ansible workflow automation: design, create, validate, and review playbooks and roles with orchestrated multi-agent pipelines
Ansible automation skills for Claude Code: playbook development, debugging, shell conversion, and interactive workflows