terraform-engineer

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.

1.07x

Quality

100%

Does it follow best practices?

Impact

95%

1.07x

Average score across 6 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

14%

Reusable AWS Security Group Module

Module structure and input validation

Criteria

Without context

With context

Standard file set

100%

Examples directory

100%

Input validation blocks

100%

for_each over count

100%

Variable descriptions

100%

Output descriptions

100%

Provider version pinned

87%

100%

Required Terraform version

100%

Tagging support

100%

snake_case naming

100%

No hardcoded values

100%

Dynamic blocks for rules

66%

100%

98%

Terraform State Infrastructure for Multi-Environment Platform

Remote state backend setup

Criteria

Without context

With context

S3 backend type

85%

100%

State encryption enabled

100%

DynamoDB locking

100%

S3 versioning enabled

100%

Server-side encryption config

100%

Public access blocked

100%

HTTPS-only bucket policy

100%

Separate state per environment

100%

No local state in production guidance

57%

71%

State file not committed

100%

Provider version pinned

100%

Resource tagging

100%

AWS Provider Setup and Developer Tooling for a New Terraform Project

Provider configuration and developer tooling

Criteria

Without context

With context

Provider version constraint

100%

Terraform version constraint

100%

Provider default_tags

100%

No hardcoded credentials

100%

Env var or IAM credential guidance

87%

100%

Pre-commit terraform_fmt hook

100%

Pre-commit terraform_validate hook

100%

Pre-commit terraform_tflint hook

100%

TFLint naming rule

100%

locals common_tags

100%

Required tags coverage

100%

No .terraform dir or state files

100%

93%

20%

Multi-Environment SaaS Platform Infrastructure

DRY multi-environment workspace config

Criteria

Without context

With context

Workspace-aware locals

100%

Environment-based sizing

100%

Data source for AMI

100%

for_each over count

12%

common_tags local

77%

100%

Tags merged on resources

62%

100%

Name prefix local

100%

No hardcoded env values

66%

100%

Provider version constraint

100%

No hardcoded credentials

100%

tfvars example file

71%

100%

Design notes file

100%

Standardised Terraform Deployment Workflow

Validation and apply workflow with error recovery

Criteria

Without context

With context

fmt before validate

100%

validate before tflint

100%

tflint before plan

100%

plan with -out flag

100%

apply from saved plan

100%

State drift recovery

100%

Provider auth recovery

100%

Dependency error recovery

100%

Re-validate after fix

80%

100%

No .terraform directory

100%

No state files committed

100%

Provider version pinned

100%

82%

Production-Ready RDS Database Module

Secure module with sensitive vars and least-privilege IAM

Criteria

Without context

With context

sensitive = true on password var

66%

55%

No secret default values

100%

Secrets manager reference

100%

50%

Least-privilege IAM actions

100%

Least-privilege IAM resources

100%

Storage encrypted

100%

lifecycle prevent_destroy

Input validation blocks

100%

All vars documented

100%

All outputs documented

100%

tfvars example file

100%

Design notes file

100%

No hardcoded credentials

100%

Repository: jeffallan/claude-skills
Commit: 5b76101

Evaluated: 27 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Reusable AWS Security Group Module Terraform State Infrastructure for Multi-Environment Platform AWS Provider Setup and Developer Tooling for a New Terraform Project Multi-Environment SaaS Platform Infrastructure Standardised Terraform Deployment Workflow Production-Ready RDS Database Module

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.