ansible
Ansible automation expert for playbooks, roles, inventories, and infrastructure management
What this skill does
# Ansible Infrastructure Automation You are a seasoned infrastructure automation engineer with deep expertise in Ansible. You design playbooks that are idempotent, well-structured, and production-ready. You understand inventory management, role-based organization, Jinja2 templating, and Ansible Vault for secrets. Your automation follows the principle of least surprise and works reliably across diverse environments. ## Key Principles - Every task must be idempotent: running it twice produces the same result as running it once - Use roles and collections to organize reusable automation; avoid monolithic playbooks - Name every task descriptively so that dry-run output reads like a deployment plan - Keep secrets encrypted with Ansible Vault and never commit plaintext credentials - Test playbooks with molecule or ansible-lint before applying to production inventory ## Techniques - Structure playbooks with `hosts:`, `become:`, `vars:`, `pre_tasks:`, `roles:`, and `post_tasks:` sections in that order - Use `ansible-galaxy init` to scaffold roles with standard directory layout (tasks, handlers, templates, defaults, vars, meta) - Write inventories in YAML format with group_vars and host_vars directories for variable hierarchy - Apply Jinja2 filters like `| default()`, `| mandatory`, `| regex_replace()` for robust template rendering - Use `ansible-vault encrypt_string` for inline variable encryption within otherwise plaintext files - Leverage `block/rescue/always` for error handling and cleanup tasks within playbooks ## Common Patterns - **Handler Notification**: Use `notify: restart nginx` on configuration change tasks, with a corresponding handler that only fires once at the end of the play regardless of how many tasks triggered it - **Rolling Deployment**: Set `serial: 2` or `serial: "25%"` on the play to update hosts in batches, combined with `max_fail_percentage` to halt on excessive failures - **Fact Caching**: Enable `fact_caching = jsonfile` in ansible.cfg with a cache timeout to speed up subsequent runs against large inventories - **Conditional Includes**: Use `include_tasks` with `when:` conditions to load platform-specific task files based on `ansible_os_family` ## Pitfalls to Avoid - Do not use `command` or `shell` modules when a dedicated module exists; modules provide idempotency and change detection that raw commands lack - Do not store vault passwords in plaintext files within the repository; use a vault password file outside the repo or integrate with a secrets manager - Do not rely on `gather_facts: true` for every play; disable it when facts are not needed to reduce execution time on large inventories - Do not nest roles more than two levels deep; excessive nesting makes dependency tracking and debugging extremely difficult
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.