ansible-expert
Use when implementing ansible functionality with production-grade patterns and safeguards.
- License 许可
- MIT
- 最近更新
- 2026-04-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- ansible-expert
- metadata
- { "hermes": { "tags": [ "codex-agent", "devops-cloud-infra" ], "source": "codex-field-kit/devops-cloud-infra" } }
- description
- Use when implementing ansible functionality with production-grade patterns and safeguards.
03 SKILL.md 正文
Ansible Expert
Focus Areas
- Effective use of Ansible modules for various tasks
- Configuration management across multiple platforms
- Developing scalable and reusable playbooks and roles
- Secure credential management using Ansible Vault
- Leveraging dynamic inventory for flexible infrastructure
- Implementing idempotent playbooks reliably
- Integrating Ansible with CI/CD pipelines seamlessly
- Orchestrating complex multi-tier deployments efficiently
- Utilizing Jinja2 templates for dynamic configurations
- Managing infrastructure as code with version control
Approach
- Define clear inventory files and grouping strategies
- Write modular and reusable roles for common tasks
- Adopt version control for playbook management
- Test playbooks in staging environments before production
- Utilize variables and facts to abstract configurations
- Handle errors gracefully and ensure consistent state
- Optimize playbooks for faster execution and concurrency
- Follow Ansible best practices and community guidelines
- Keep Ansible updated to leverage the latest features
- Document playbooks and roles extensively for team usage
Quality Checklist
- Playbooks execute idempotently without unintended changes
- Roles and playbooks are reusable and parameterized
- Inventory files are well-structured with logical grouping
- Secrets are encrypted with Ansible Vault securely
- Extensive logging is in place for troubleshooting
- Ansible linting and validation tools are used routinely
- Jinja2 templates are efficient and error-free
- Provisioning process handles failover and rollback
- Documentation is complete and accessible to team members
- Playbooks and roles comply with organizational standards
Output
- Well-structured and maintainable Ansible playbooks
- Scalable roles that encapsulate distinct functionalities
- Dynamic and secure inventory management solutions
- Automated deployment pipelines incorporating Ansible
- High-quality documentation and user guides
- Audit logs and system states for compliance checks
- Ansible Vault for secure credentials management
- Refined processes for efficient playbook execution
- Robust error handling and recovery procedures
- Continuous improvement roadmap for Ansible adoption
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
super-swarm-spark
Only to be triggered by explicit super-swarm-spark commands.
role-creator
Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).
read-github
Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo
planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.