Claude Ansible Skills
leogallego/claude-ansible-skills
Automação Ansible com boas práticas Red Hat e validação em tempo real
Ver no GitHubColeção de skills para Claude Code que automatiza desenvolvimento Ansible seguindo as boas práticas da Red Hat Communities of Practice. Inclui revisão de código, scaffolding de roles/collections/execution environments e análise filosófica contra os princípios Zen do Ansible.
Instalação
npx convez-ai leogallego/claude-ansible-skills1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Revisar playbooks e roles contra padrões CoP automaticamente
- Gerar roles, collections e execution environments conformes
- Validar simplicity e readability de código Ansible
- Integrar lint, handlers e templates inteligentes em projetos existentes
Veredito

Excelente para times que adotam Ansible em escala e precisam enforçar padrões. O scaffolding inteligente e a revisão baseada em CoP economizam horas de design arquitetural. Requer familiaridade com Ansible e fluxo Claude Code.
README
A tradução para o português deste README ainda está na fila.
claude-ansible-skills
A collection of Claude Code skills for Ansible automation development following Red Hat Communities of Practice (CoP) good practices.
Skills
ansible-good-practices
Review Ansible code against Red Hat CoP automation good practices loaded from per-section AsciiDoc references.
- Section-selective loading — loads only the reference sections relevant to the files being reviewed
- Severity classification: ERROR, WARNING, INFO
- Diff-aware mode — review only changed files
- Category filtering — focus on specific rule categories
- ansible-lint integration with CoP rule cross-referencing
- Parallel review with subagents for large projects
- Auto-fix offer after reporting
ansible-scaffold-role
Scaffold a new Ansible role fully compliant with CoP rules.
- Interactive variable builder — asks what the role manages (packages, services, configs, users, firewall, storage) and generates realistic defaults, tasks, handlers, and templates
- Task componentization — splits complex roles into
install.yml,configure.yml,service.ymlwith sub-task name prefixes - Smart handler generation — creates real handlers (restart, reload, validate) based on role purpose
- Collection-aware — uses
ansible-creatorinside collections, manual creation otherwise - Falls back to manual creation when
ansible-creatoris not installed
ansible-scaffold-collection
Scaffold a new Ansible content collection using ansible-creator, then customize for full CoP compliance.
- Plugin scaffolding — generates modules, filters, lookup, and action plugin skeletons with proper docstrings and FQCN examples
- Delegates role creation to the full ansible-scaffold-role skill process
- CI/CD pipeline generation for GitHub Actions or GitLab CI (lint, test, build, publish)
- Changelog setup with
antsibull-changelog - Generates collection-level CLAUDE.md for future Claude Code sessions
- Falls back to manual creation when
ansible-creatoris not installed
ansible-scaffold-ee
Scaffold a new Ansible execution environment project using ansible-creator.
- Dependency introspection — auto-detects collections, roles, Python, and system deps from existing project files
- External dependency files — generates
requirements.yml,requirements.txt, andbindep.txtfor non-trivial EEs - CI/CD pipeline generation for GitHub Actions or GitLab CI (build, test, push to registry)
- Falls back to manual creation when
ansible-creatoris not installed
ansible-zen
Display the Zen of Ansible and review code against its 20 principles.
- Display mode — prints the full Zen and explains a random principle with a practical example
- Review mode — evaluates Ansible code for simplicity, readability, and clarity
- Zen Score (1-10) rating with justification
- Principle-grouped findings with before/after code improvements
- Complements ansible-good-practices with philosophical guidance
Project Structure
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.
Installation
Plugin install (recommended)
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-scaffold-role
/plugin install ansible-scaffold-collection
/plugin install ansible-scaffold-ee
/plugin install ansible-zen
Manual install (symlinks)
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-scaffold-role/skills/ansible-scaffold-role ~/.claude/skills/ansible-scaffold-role
All skills at once at profile level:
mkdir -p ~/.claude/skills
for plugin in ~/claude-ansible-skills/ansible-*/; do
skill=$(basename "$plugin")
ln -s "$plugin/skills/$skill" ~/.claude/skills/"$skill"
done
Usage
Once installed, invoke skills in Claude Code with their slash command:
/ansible-good-practices
/ansible-scaffold-role
/ansible-scaffold-collection
/ansible-scaffold-ee
/ansible-zen
Dependencies
- ansible-creator — used by scaffold skills to generate base skeletons (optional — skills fall back to manual creation)
- ansible-lint — used by the review skill for cross-referencing (optional)
- CoP rules — skills load rules from bundled
references/*.adocfiles (per-section AsciiDoc from redhat-cop/automation-good-practices), with GitHub fetch as fallback and CLAUDE.md as last resort
Contributing
We welcome contributions from the community. This project follows the Red Hat Communities of Practice contributing guidelines.
Development workflow
- Fork the repository
- Create a branch for your work
- Open a pull request following the guidelines below
- Address reviewer feedback
- A maintainer will merge once approved — do not merge your own PRs
Adding a new skill
- Create a directory named
ansible-<skill-name>/ - Add
.claude-plugin/plugin.jsonwith name, version, and description - Add
skills/<skill-name>/SKILL.mdwith frontmatter and prompt body - Follow the SKILL.md format:
- Description must include what the skill does, when to use it, and trigger phrases users would say
- Add
argument-hintif the skill accepts arguments - Add
disable-model-invocation: truefor skills with side effects - Keep SKILL.md under 500 lines; move detailed docs to
references/
- Skills should reference CLAUDE.md rules rather than duplicating them
- Run
node scripts/gen-marketplace.jsto regenerate the marketplace index - Commit the updated
marketplace.jsonalongside your changes
Modifying existing skills
- Read the skill's SKILL.md before modifying — understand the full prompt
- After changes, run
node scripts/gen-marketplace.jsto update plugin metadata - Squash commits whenever possible
Best practices
- Write clear, descriptive PR titles and summaries
- Do not commit directly to the main branch
- Review existing skills to prevent duplication
- Test your skill by invoking it with
/skill-namein Claude Code - Use
snake_casewith hyphens for directory names (matchingansible-*)
Reporting issues
Open an issue on GitHub for:
- Bug reports — describe the skill, the input, and the unexpected behavior
- Feature requests — describe the use case and the expected outcome
- Rule updates — if Red Hat CoP good practices change upstream
License
GPL-3.0-or-later