DevOps & Infra
ansible-workflow - Claude MCP Skill
Ansible automation workflow guidelines. Activate when working with Ansible playbooks, ansible-playbook, inventory files (.yml, .ini), or Ansible-specific patterns.
SEO Guide: Enhance your AI agent with the ansible-workflow tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to ansible automation workflow guidelines. activate when working with ansible playbooks, ansible-playbo... Download and configure this skill to unlock new capabilities for your AI workflow.
Documentation
SKILL.mdThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
# Ansible Workflow
## Tool Grid
| Task | Tool | Command |
|------|------|---------|
| Lint | ansible-lint | `ansible-lint` |
| YAML lint | yamllint | `yamllint .` |
| Syntax check | ansible | `ansible-playbook --syntax-check` |
| Dry run | ansible | `ansible-playbook --check` |
| Run | ansible | `ansible-playbook playbook.yml` |
| Test roles | molecule | `molecule test` |
| Encrypt | sops | `sops -e secrets.yml` |
| Decrypt | sops | `sops -d secrets.yml` |
## Runtime Requirements
- Ansible Core 2.18+ with Python 3.12+
- ansible-lint and yamllint installed
- SOPS for secrets management (RECOMMENDED over ansible-vault for GitOps)
- Molecule + docker driver for role testing
## Code Standards
### FQCN Requirement
All module names MUST use Fully Qualified Collection Names (FQCN):
```yaml
# CORRECT
- name: Copy configuration file
ansible.builtin.copy:
src: app.conf
dest: /etc/app/app.conf
# INCORRECT - DO NOT USE
- name: Copy configuration file
copy:
src: app.conf
dest: /etc/app/app.conf
```
### Linting
All playbooks and roles MUST pass linting before commit:
```bash
# Run both linters
ansible-lint && yamllint .
```
Configuration templates available in `assets/`:
- `.ansible-lint.template` - Production profile with strict mode
- `.yamllint.template` - YAML linting with 120 char lines
### Sensitive Data
Tasks handling sensitive data MUST use `no_log: true`:
```yaml
- name: Set database password
ansible.builtin.shell: |
mysql -u root -p'{{ db_root_password }}' -e "SET PASSWORD..."
no_log: true
- name: Create API token
ansible.builtin.uri:
url: "{{ api_endpoint }}/tokens"
headers:
Authorization: "Bearer {{ admin_token }}"
no_log: true
register: token_result
```
## Secrets Management
### SOPS (RECOMMENDED for GitOps)
SOPS is RECOMMENDED over ansible-vault for GitOps workflows:
```yaml
# .sops.yaml
creation_rules:
- path_regex: .*vars/secrets\.yml$
age: age1xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
```
```bash
# Encrypt
sops -e vars/secrets.yml > vars/secrets.enc.yml
# Decrypt inline during playbook
sops -d vars/secrets.enc.yml | ansible-playbook -e @/dev/stdin playbook.yml
```
### ansible-vault (Legacy)
When ansible-vault is required:
```bash
# Encrypt variable file
ansible-vault encrypt group_vars/prod/vault.yml
# Run with vault
ansible-playbook --ask-vault-pass playbook.yml
```
## Project Structure
### Environment-Based Inventory
```
inventories/
āāā prod/
ā āāā hosts.yml
ā āāā group_vars/
ā ā āāā all.yml
ā ā āāā webservers.yml
ā ā āāā databases.yml
ā āāā host_vars/
āāā staging/
ā āāā hosts.yml
ā āāā group_vars/
āāā dev/
āāā hosts.yml
āāā group_vars/
```
### group_vars Organization
Organize group_vars by role name for clarity:
```
group_vars/
āāā all/
ā āāā main.yml # Common variables
ā āāā secrets.enc.yml # SOPS-encrypted secrets
āāā webservers/
ā āāā nginx.yml # Role: nginx
ā āāā ssl.yml # Role: ssl_certificates
āāā databases/
āāā postgresql.yml # Role: postgresql
āāā backup.yml # Role: db_backup
```
### Role Structure
Roles SHOULD be single-purpose:
```
roles/
āāā nginx/ # Web server only
āāā ssl_certificates/ # SSL management only
āāā postgresql/ # Database only
āāā app_deploy/ # Application deployment only
```
## Dynamic Inventories
### AWS EC2
```yaml
# inventories/aws/aws_ec2.yml
plugin: amazon.aws.aws_ec2
regions:
- us-east-1
- us-west-2
keyed_groups:
- key: tags.Environment
prefix: env
- key: tags.Role
prefix: role
filters:
instance-state-name: running
hostnames:
- private-ip-address
compose:
ansible_host: private_ip_address
```
### Azure RM
```yaml
# inventories/azure/azure_rm.yml
plugin: azure.azcollection.azure_rm
auth_source: auto
include_vm_resource_groups:
- production-rg
- staging-rg
keyed_groups:
- key: tags.Environment
prefix: env
hostnames:
- private_ipv4_addresses
```
### GCP Compute
```yaml
# inventories/gcp/gcp_compute.yml
plugin: google.cloud.gcp_compute
projects:
- my-project-id
zones:
- us-central1-a
- us-central1-b
keyed_groups:
- key: labels.environment
prefix: env
hostnames:
- private_ip
```
## Handler Patterns
### Proper Handler Usage
```yaml
# tasks/main.yml
- name: Update nginx configuration
ansible.builtin.template:
src: nginx.conf.j2
dest: /etc/nginx/nginx.conf
notify: Restart nginx
- name: Update SSL certificate
ansible.builtin.copy:
src: "{{ ssl_cert_file }}"
dest: /etc/nginx/ssl/cert.pem
notify:
- Validate nginx config
- Reload nginx
# handlers/main.yml
- name: Validate nginx config
ansible.builtin.command: nginx -t
changed_when: false
- name: Reload nginx
ansible.builtin.systemd:
name: nginx
state: reloaded
- name: Restart nginx
ansible.builtin.systemd:
name: nginx
state: restarted
```
### Handler Execution Order
Handlers execute in definition order, not notification order. Define handlers in logical sequence (validate -> reload -> restart).
## Variable Precedence
Ansible variable precedence (highest to lowest):
1. Extra vars (`-e "var=value"`)
2. Task vars (in task definition)
3. Block vars
4. Role and include vars
5. Set facts / registered vars
6. Play vars_files
7. Play vars
8. Host facts
9. Playbook host_vars
10. Inventory host_vars
11. Playbook group_vars
12. Inventory group_vars
13. Role defaults
### Best Practices
```yaml
# Use role defaults for safe defaults
# roles/nginx/defaults/main.yml
nginx_worker_processes: auto
nginx_worker_connections: 1024
# Use group_vars for environment-specific overrides
# group_vars/prod/nginx.yml
nginx_worker_connections: 4096
# Use extra vars for one-time overrides only
ansible-playbook playbook.yml -e "nginx_worker_connections=8192"
```
## Molecule Testing
### Role Testing Setup
```yaml
# roles/nginx/molecule/default/molecule.yml
dependency:
name: galaxy
driver:
name: docker
platforms:
- name: instance
image: geerlingguy/docker-${MOLECULE_DISTRO:-rockylinux9}-ansible
pre_build_image: true
privileged: true
command: /usr/sbin/init
provisioner:
name: ansible
verifier:
name: ansible
```
### Running Tests
```bash
molecule test # Full test cycle
molecule converge # Apply role
molecule verify # Run verification
molecule destroy # Cleanup
```
## Performance Optimization
### ansible.cfg Settings
Use the template at `assets/ansible.cfg.template`:
- `forks = 20` - Parallel execution
- `pipelining = True` - Reduce SSH operations
- `gathering = smart` - Cache facts
- `fact_caching = jsonfile` - Persist facts
### Task Optimization
```yaml
# Use async for long-running tasks
- name: Upgrade all packages
ansible.builtin.dnf:
name: "*"
state: latest
async: 600
poll: 10
# Use free strategy for independent tasks
- hosts: all
strategy: free
tasks:
- name: Independent task 1
ansible.builtin.command: /opt/script1.sh
- name: Independent task 2
ansible.builtin.command: /opt/script2.sh
```
## Pre-Commit Checklist
Before committing Ansible code:
1. [ ] `ansible-lint` passes with no warnings
2. [ ] `yamllint .` passes
3. [ ] `ansible-playbook --syntax-check` passes
4. [ ] All modules use FQCN
5. [ ] Sensitive tasks have `no_log: true`
6. [ ] Secrets encrypted with SOPS (or vault)
7. [ ] Molecule tests pass for modified roles
8. [ ] Variables documented in role READMESignals
Information
- Repository
- ilude/claude-code-config
- Author
- ilude
- Last Sync
- 3/12/2026
- Repo Updated
- 2/15/2026
- Created
- 1/12/2026
Reviews (0)
No reviews yet. Be the first to review this skill!
Related Skills
upgrade-nodejs
Upgrading Bun's Self-Reported Node.js Version
cursorrules
CrewAI Development Rules
cn-check
Install and run the Continue CLI (`cn`) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
CLAUDE
CLAUDE.md
Related Guides
Bear Notes Claude Skill: Your AI-Powered Note-Taking Assistant
Learn how to use the bear-notes Claude skill. Complete guide with installation instructions and examples.
Mastering tmux with Claude: A Complete Guide to the tmux Claude Skill
Learn how to use the tmux Claude skill. Complete guide with installation instructions and examples.
OpenAI Whisper API Claude Skill: Complete Guide to AI-Powered Audio Transcription
Learn how to use the openai-whisper-api Claude skill. Complete guide with installation instructions and examples.