ansible
Skill4 starsChanged 6 months agoMITView on GitHub
How to run and manage Ansible operations. You MUST load this skill when working with the `ansible` command.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Lukk17/agent-standardstheir own version, first seen Nov 7, 2026
- iuliandita/skillstheir own version, first seen Oct 14, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- greedychipmunk/agent-skillstheir own version, first seen May 25, 2026
- julweber/ai_agent_skillstheir own version, first seen Mar 20, 2026
- Kubementat/ai_agent_skillstheir own version, first seen Mar 20, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- greedychipmunk/agent-skills★ 24same name
- G1Joshi/Agent-Skills★ 15same name
- iuliandita/skills★ 11same name
- julweber/ai_agent_skills★ 2same name
- Kubementat/ai_agent_skills★ 2same name
- Lukk17/agent-standards★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository124 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- .vscode/AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-log-analysisSkill
- agent-mdSkill
- agent-md-writerSkill
- agent-skill-md-writerSkill
- agentskillsSkill
- agents-md-writerSkill
- ai-prompt-writerSkill
- apache-airflow-apiSkill
- apache-airflow-dagsSkill
- astro-cliSkill
- astronomer-docsSkill
- awesome-copilotSkill
- brainstorm-agent-runsSkill
- brainstorm-github-prSkill
- brainstormSkill
- catSkill
- chrome-devtoolsSkill
- claude-docsSkill
- codeqlSkill
- code-reviewSkill
- code-tourSkill
- coding-standard-writerSkill
- context-aware-opsSkill
- copilot-cliSkill
- copilot-docsSkill
- critical-thinkingSkill
- datadog-agentSkill
- datadog-apiSkill
- datadog-mcpSkill
- datadog-monitorsSkill
- datadog-pulumiSkill
- devcontainerSkill
- dictationSkill
- direnvSkill
- dockerfileSkill
- dockerSkill
- docs-reviewSkill
- docs-writerSkill
- dot-claudeSkill
- dotfilesSkill
- dot-githubSkill
- editorconfigSkill
- fact-writerSkill
- gdpr-compliantSkill
- gh-agent-taskSkill
- gh-apiSkill
- gh-aw-compileSkill
- gh-aw-firewall-debugSkill
- gh-aw-firewallSkill
- gh-aw-newSkill
- gh-awSkill
- gh-aw-troubleshootingSkill
- gh-codespaceSkill
- gh-issueSkill
- gh-modelsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
When the task explicitly requires agentic AI decision-making loops (Ansible is deterministic).
- Very specific: line 34
If you encounter hangs during Ansible execution, especially when interacting with package managers like apt on Debian/Ubuntu systems:
- Very specific: line 37
Use the DEBIAN_FRONTEND environment variable to prevent prompts from hanging the process.
- Distinctive: line 43
Do NOT use mocking to work around unexpected errors:
- Very specific: line 45
Never use mock_modules or mock_roles to bypass tasks that are failing due to environment-specific issues or other "shouldn't happen" errors.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- markdownlint-disable MD013 MD023 MD031 MD032 -->Ansible Operations
When to Use
- Agent needs to execute Ansible playbooks or commands.
- User needs to run Ansible automation scripts.
- Troubleshooting hanging issues during Ansible execution.
When Not to Use
- For localized script automation on a single machine where simple shell scripts suffice.
- For managing ephemeral, immutable container infrastructure better suited for Terraform or Dockerfiles.
- When the task explicitly requires agentic AI decision-making loops (Ansible is deterministic).
Common Pitfalls
- Interactive Hangs: Failing to set
DEBIAN_FRONTEND=noninteractiveor handling sudo passwords poorly, causing the agent to hang indefinitely. - Ignoring Idempotency: Writing raw shell commands (
ansible.builtin.shell) instead of using native Ansible modules, breaking the idempotency guarantee of playbooks. - Masking Errors: Using
ignore_errors: yesto bypass failures rather than fixing the underlying system state.
Troubleshooting
Ansible Environment issues
If you encounter hangs during Ansible execution, especially when interacting with package managers
like apt on Debian/Ubuntu systems:
- Use the
DEBIAN_FRONTENDenvironment variable to prevent prompts from hanging the process. - Set
DEBIAN_FRONTEND=noninteractivewhen running your Ansible commands or in your playbook environment. - Example:
DEBIAN_FRONTEND=noninteractive ansible-playbook playbook.yml
Prohibiting Mocking for Workarounds
Do NOT use mocking to work around unexpected errors:
- Never use
mock_modulesormock_rolesto bypass tasks that are failing due to environment-specific issues or other "shouldn't happen" errors. - Underlying issues must be fixed directly; do not mask failures with mocks to unblock progress.
Performance Profiling
To profile the execution time of your playbooks and roles, you can enable the profile_tasks callback plugin.
This is useful for identifying slow tasks and optimizing your automation.
- Enable the plugin by adding it to your
ansible.cfgfile under[defaults]or via environment variables. - Using environment variables:
ANSIBLE_CALLBACKS_ENABLED=profile_tasks ansible-playbook playbook.yml In
ansible.cfg:[defaults] callbacks_enabled = ansible.posix.profile_tasks
Related Skills
- molecule: You MUST load this skill when running or managing Molecule tests for Ansible.
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.

