Agent skill · software engineering · aiskillstore
devops-iac-engineer
Implements infrastructure as code using Terraform, Kubernetes, and cloud platforms. Designs scalable architectures, CI/CD pipelines, and observability solutions. Provides security-first DevOps practices and site reliability engineering guidance.
Why this skill is useful
Provides detailed workflows and templates for implementing Infrastructure as Code with Terraform and Kubernetes that the AI wouldn't reliably generate on its own.
What it needs
Requires kubernetes, terraform installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
DevOps IaC Engineer This Skill helps DevOps teams design, implement, and maintain cloud infrastructure using Infrastructure as Code principles. Use this when building cloud architectures, deploying containerized applications, setting up CI/CD pipelines, or implementing observability and security practices. Quick Navigation Terraform & IaC: See terraform.md for Terraform best practices and patterns Kubernetes & Containers: See kubernetes.md for container orchestration Cloud Platforms: See cloudplatforms.md for AWS, Azure, GCP guidance CI/CD Pipelines: See cicd.md for pipeline design and GitOps Observability: See observability.md for monitoring and logging Security: See security.md for DevSecOps practices Templates & Tools: See templates.md for ready-to-use templates Core Principles Key DevOps Terminology (Consistent Throughout) Infrastructure as Code (IaC): Managing infrastructure through declarative code files GitOps: Using Git as the single source of truth for infrastructure and applications Immutable Infrastructure: Infrastructure components that are replaced rather than modified Service Mesh: Infrastructure layer for service-to-service communication Observability: Ability to understand system state from external outputs (logs, metrics, traces) SLI/SLO/SLA: Service Level Indicators/Objectives/Agreements for reliability RTO/RPO: Recovery Time Objective/Recovery Point Objective for disaster recovery Workflow: Infrastructure Implementation When implementing infrastructure, follow this structured approach: 1. Understand Requirements What is the business need? (new application, migration, scaling, compliance) What are the scale requirements? (traffic, data, geographic distribution) What are the constraints? (budget, timeline, regulatory) What are the dependencies? (existing systems, data sources) 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/devops-iac-engineer