Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jeffallan avatar

Terraform Engineer

  • 4k installs
  • 10.8k repo stars
  • Updated May 20, 2026
  • jeffallan/claude-skills

terraform-engineer is an agent skill for implement terraform modules and infrastructure across aws, azure, or gcp with state and iam patterns.

About

The terraform-engineer skill Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing. Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns. 1. Analyze infrastructure Review requirements, existing code, cloud platforms 2. Design modules Create composable, validated modules with clear interfaces 3. Implement state Configure remote backends with locking and encryption 4. Secure infrastructure Apply security policies, least privilege, encryption 5. Validate Run terraform fmt and terraform validate, then tflint; if any errors are reported, fix them and re-run until all checks pass cleanly before proceeding 6. Plan and apply Run terraform plan -out=tfplan, review output carefully, then terraform apply tfplan; if the plan fails, see error recovery below Validation failures (step 5): Fix repo.

  • Analyze infrastructure — Review requirements, existing code, cloud platforms
  • Design modules — Create composable, validated modules with clear interfaces
  • Implement state — Configure remote backends with locking and encryption
  • Secure infrastructure — Apply security policies, least privilege, encryption
  • Validate — Run terraform fmt and terraform validate, then tflint; if any errors are reported, fix them and re-run until

Terraform Engineer by the numbers

  • 4,002 all-time installs (skills.sh)
  • +113 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #38 of 1,453 DevOps & CI/CD skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

terraform-engineer capabilities & compatibility

Capabilities
analyze infrastructure — review requirements, ex · design modules — create composable, validated mo · implement state — configure remote backends with · secure infrastructure — apply security policies, · validate — run terraform fmt and terraform valid
Works with
terraform · aws
Use cases
devops · ci cd
From the docs

What terraform-engineer says it does

Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.
SKILL.md
1. **Analyze infrastructure** — Review requirements, existing code, cloud platforms
SKILL.md
2. **Design modules** — Create composable, validated modules with clear interfaces
SKILL.md
npx skills add https://github.com/jeffallan/claude-skills --skill terraform-engineer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4k
repo stars10.8k
Security audit3 / 3 scanners passed
Last updatedMay 20, 2026
Repositoryjeffallan/claude-skills

How do I implement terraform modules and infrastructure across aws, azure, or gcp with state and iam patterns with documented agent guidance?

Implement Terraform modules and infrastructure across AWS, Azure, or GCP with state and IAM patterns.

Who is it for?

Developers who need devops & ci/cd help during build work.

Skip if: Skip when the task falls outside DevOps & CI/CD scope described in SKILL.md.

When should I use this skill?

Implement Terraform modules and infrastructure across AWS, Azure, or GCP with state and IAM patterns.

What you get

Completed devops & ci/cd workflow aligned with SKILL.md steps and validation.

  • Terraform module files
  • Locals and variable definitions
  • Production HCL resource blocks

By the numbers

  • Analyze infrastructure — Review requirements, existing code, cloud platforms
  • Design modules — Create composable, validated modules with clear interfaces
  • Implement state — Configure remote backends with locking and encryption

Files

SKILL.mdMarkdownGitHub ↗

Terraform Engineer

Senior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.

Core Workflow

1. Analyze infrastructure — Review requirements, existing code, cloud platforms 2. Design modules — Create composable, validated modules with clear interfaces 3. Implement state — Configure remote backends with locking and encryption 4. Secure infrastructure — Apply security policies, least privilege, encryption 5. Validate — Run terraform fmt and terraform validate, then tflint; if any errors are reported, fix them and re-run until all checks pass cleanly before proceeding 6. Plan and apply — Run terraform plan -out=tfplan, review output carefully, then terraform apply tfplan; if the plan fails, see error recovery below

Error Recovery

Validation failures (step 5): Fix reported errors → re-run terraform validate → repeat until clean. For tflint warnings, address rule violations before proceeding.

Plan failures (step 6):

  • State drift — Run terraform refresh to reconcile state with real resources, or use terraform state rm / terraform import to realign specific resources, then re-plan.
  • Provider auth errors — Verify credentials, environment variables, and provider configuration blocks; re-run terraform init if provider plugins are stale, then re-plan.
  • Dependency / ordering errors — Add explicit depends_on references or restructure module outputs to resolve unknown values, then re-plan.

After any fix, return to step 5 to re-validate before re-running the plan.

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Modulesreferences/module-patterns.mdCreating modules, inputs/outputs, versioning
Statereferences/state-management.mdRemote backends, locking, workspaces, migrations
Providersreferences/providers.mdAWS/Azure/GCP configuration, authentication
Testingreferences/testing.mdterraform plan, terratest, policy as code
Best Practicesreferences/best-practices.mdDRY patterns, naming, security, cost tracking

Constraints

MUST DO

  • Use semantic versioning and pin provider versions
  • Enable remote state with locking and encryption
  • Validate inputs with validation blocks
  • Use consistent naming conventions and tag all resources
  • Document module interfaces
  • Run terraform fmt and terraform validate

MUST NOT DO

  • Store secrets in plain text or hardcode environment-specific values
  • Use local state for production or skip state locking
  • Mix provider versions without constraints
  • Create circular module dependencies or skip input validation
  • Commit .terraform directories

Code Examples

Minimal Module Structure

`main.tf`

resource "aws_s3_bucket" "this" {
  bucket = var.bucket_name
  tags   = var.tags
}

`variables.tf`

variable "bucket_name" {
  description = "Name of the S3 bucket"
  type        = string

  validation {
    condition     = length(var.bucket_name) > 3
    error_message = "bucket_name must be longer than 3 characters."
  }
}

variable "tags" {
  description = "Tags to apply to all resources"
  type        = map(string)
  default     = {}
}

`outputs.tf`

output "bucket_id" {
  description = "ID of the created S3 bucket"
  value       = aws_s3_bucket.this.id
}

Remote Backend Configuration (S3 + DynamoDB)

terraform {
  backend "s3" {
    bucket         = "my-tf-state"
    key            = "env/prod/terraform.tfstate"
    region         = "us-east-1"
    encrypt        = true
    dynamodb_table = "terraform-lock"
  }
}

Provider Version Pinning

terraform {
  required_version = ">= 1.5.0"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.0"
    }
    azurerm = {
      source  = "hashicorp/azurerm"
      version = "~> 3.0"
    }
  }
}

Output Format

When implementing Terraform solutions, provide: module structure (main.tf, variables.tf, outputs.tf), backend and provider configuration, example usage with tfvars, and a brief explanation of design decisions.

Documentation

Related skills

How it compares

terraform-engineer is an agent skill for implement terraform modules and infrastructure across aws, azure, or gcp with state and iam patterns, not a generic alternative.

FAQ

Who is terraform-engineer for?

Developers using DevOps & CI/CD workflows with agent-guided SKILL.md steps.

When should I use terraform-engineer?

Implement Terraform modules and infrastructure across AWS, Azure, or GCP with state and IAM patterns.

Is terraform-engineer safe to install?

Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.