ansible-ops
Ansible playbook management covering inventory, vault, syntax checks, and idempotency. Use when writing or running Ansible playbooks, configuring servers or deploying services, or managing secrets with Ansible Vault.
- License 许可
- MIT
- 所属仓库
- muratovv/ai-hats
- 最近更新
- 2026-11-05
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- ansible-ops
- license
- MIT
- description
- Ansible playbook management covering inventory, vault, syntax checks, and idempotency. Use when writing or running Ansible playbooks, configuring servers or deploying services, or managing secrets with Ansible Vault.
03 SKILL.md 正文
Ansible Ops
Manage infrastructure using Ansible playbooks and roles.
When to Use
Config & app deployment onto hosts that already exist — playbooks, roles, vault. The sibling for provisioning the infrastructure itself (creating hosts, networks, managed services + their state) is terraform-expert: declare the box with Terraform, configure what runs on it with Ansible. Don't reach here to stand up infrastructure.
Conventions
- Inventory: Always explicitly specify the inventory file with
-i. - Vault Safety: Never run commands requiring interactive password entry (
--ask-vault-pass). Generate the command for the user to run instead. - Syntax First: Run
ansible-lintoransible-playbook --syntax-checkbefore presenting a playbook. - Timeout: Prefix playbook runs with
timeout 300sto prevent hangs. - Idempotency: Every playbook must be safe to re-run. Use
creates:,when:, and handler-based restarts.
Anti-Patterns
- Running playbooks without
--syntax-checkfirst — catch errors before execution - Interactive password prompts (
--ask-vault-pass) — generate commands for the user - Non-idempotent tasks — every playbook must be safe to re-run
04 同仓库更多 Skills
tool-evaluation-protocol
Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML/LLM frameworks, testing approaches), or following up on a hype-driven recommendation.
systematic-debugging
4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.
skill-template
Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.
skill-optimization
Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.
silent-fallback-gate
PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.
retro-to-framework
Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.