Ansible automation and configuration management patterns. Use when writing Ansible playbooks, roles, or automating infrastructure configuration and deployment tasks.
Provides Ansible automation patterns and best practices for writing playbooks, roles, and infrastructure configuration. Triggers when creating or editing Ansible files with `.yml` extension or when discussing infrastructure automation tasks.
/plugin marketplace add jpoutrin/product-forge/plugin install devops-data@product-forge-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides Ansible automation patterns and best practices.
---
- name: Configure web servers
hosts: webservers
become: true
vars:
http_port: 80
tasks:
- name: Install nginx
ansible.builtin.apt:
name: nginx
state: present
notify: Restart nginx
handlers:
- name: Restart nginx
ansible.builtin.service:
name: nginx
state: restarted
roles/
└── webserver/
├── defaults/main.yml # Default variables
├── handlers/main.yml # Handler definitions
├── tasks/main.yml # Task list
├── templates/ # Jinja2 templates
├── files/ # Static files
└── vars/main.yml # Role variables
# ✅ Good
- ansible.builtin.apt:
name: nginx
# ❌ Bad (ambiguous)
- apt:
name: nginx
# Tasks should be safe to run multiple times
- name: Ensure config exists
ansible.builtin.template:
src: config.j2
dest: /etc/app/config.yml
# Only changes if content differs
tasks:
- name: Update config
template:
src: nginx.conf.j2
dest: /etc/nginx/nginx.conf
notify: Restart nginx
handlers:
- name: Restart nginx
service:
name: nginx
state: restarted
[webservers]
web1.example.com
web2.example.com
[dbservers]
db1.example.com
[production:children]
webservers
dbservers
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.