ansible-interactive
Skill89 starsChanged 10 months agoMITView on GitHub
Use when guiding someone through Ansible setup step-by-step. Use when starting a new Ansible project from scratch. Use when teaching Ansible through hands-on development.
- Reads credentials
In this repository3 other files it gives its agents.
- ansible-convertSkill
- ansible-debugSkill
- ansible-playbookSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
Verify Ansible is installed: ansible --version
- Distinctive: line 83
Start simple, add one task at a time:
- Distinctive: line 106
Run again. Fix any errors before adding more.
- Very specific: line 115
Run again—verify changed=0 (idempotency)
- Distinctive: line 122
Not testing SSH before writing playbooks
- Distinctive: line 128
After completion, summarize what was done
- Distinctive: line 129
When multiple approaches exist, present options with tradeoffs
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Interactive Ansible Development
Overview
Interactive development builds automation incrementally with continuous validation. Each component is tested before adding the next. This catches errors early when they're easy to diagnose.
When to Use
- Setting up Ansible for a new environment
- Teaching someone Ansible hands-on
- Building playbooks incrementally with validation
- Troubleshooting connectivity before automation
Development Phases
Phase 1: Environment Analysis
Gather before writing any code:
| Question | Why It Matters |
| How many servers? | Affects inventory organization |
| IP addresses/hostnames? | Required for inventory |
| SSH user and key location? | Connection configuration |
| Password or key auth? | Determines SSH setup |
| Sudo with or without password? | Privilege escalation config |
| Server roles (web, db, app)? | Inventory grouping |
| Operating systems? | Module selection (apt vs yum) |
Verify Ansible is installed: ansible --version
Phase 2: Project Setup
Create minimal structure:
mkdir ansible-project && cd ansible-projectansible.cfg:
[defaults]
inventory = ./inventory
host_key_checking = False
stdout_callback = yaml
[privilege_escalation]
become = True
become_method = sudoinventory:
[webservers]
web1 ansible_host=192.168.1.10 ansible_user=admin ansible_ssh_private_key_file=~/.ssh/id_rsa
[dbservers]
db1 ansible_host=192.168.1.20 ansible_user=admin ansible_ssh_private_key_file=~/.ssh/id_rsaPhase 3: Connectivity Test
Always test before writing playbooks:
ansible all -m ping| Result | Action |
| SUCCESS | Proceed to playbooks |
| UNREACHABLE | Check ssh -v user@host |
| Permission denied | Verify key path, permissions (600) |
| Sudo password required | Add --ask-become-pass or configure NOPASSWD |
Phase 4: Incremental Playbook Development
Start simple, add one task at a time:
# playbook.yml - start with facts
---
- hosts: all
tasks:
- name: Show OS info
ansible.builtin.debug:
msg: "{{ ansible_distribution }} {{ ansible_distribution_version }}"Run: ansible-playbook playbook.yml
Then add tasks one by one, testing after each:
- name: Ensure nginx installed
ansible.builtin.package:
name: nginx
state: presentRun again. Fix any errors before adding more.
Phase 5: Validation Cycle
After each change:
ansible-playbook --syntax-check playbook.ymlansible-playbook --check --diff playbook.ymlansible-playbook playbook.yml- Run again—verify
changed=0(idempotency)
Red Flags - Stop and Debug
- Adding multiple untested tasks at once
- Skipping
--checkbefore real runs - Ignoring "changed" on second run
- Not testing SSH before writing playbooks
Communication Pattern
When guiding users:
- Explain what will happen before running commands
- After completion, summarize what was done
- When multiple approaches exist, present options with tradeoffs
- Acknowledge progress at milestones
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

