Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions
90
—
Does it follow best practices?
Impact
99%
1.45xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
VPC module creation with correct structure and naming
Standard file layout
100%
100%
Pre-commit config present
100%
100%
Attribution in README
0%
100%
Singleton 'this' naming
100%
100%
Descriptive names for multi-resources
100%
100%
for_each used for subnets
0%
100%
count for boolean toggle
100%
100%
Resource block ordering
100%
100%
Variable block ordering
100%
100%
Variable descriptions present
100%
100%
Output descriptions present
100%
100%
Output naming pattern
100%
100%
try() for optional resources
25%
100%
Locals for deletion order
12%
100%
Context-specific variable names
100%
100%
Native Terraform test authoring with mocks and set handling
Mock provider used
0%
100%
command=plan for input validation
100%
100%
command=apply for set-type blocks
0%
100%
No [0] indexing on sets
0%
100%
for expressions for set iteration
0%
100%
Validation failure test
100%
100%
Conditional resource test
100%
100%
test-plan.md explains command choices
80%
100%
test-plan.md explains mock usage
37%
100%
Tests are in .tftest.hcl files
100%
100%
CI/CD pipeline, remote state, secrets, and version pinning
Four CI/CD stages present
60%
100%
Apply restricted to main branch
100%
100%
Integration tests on main only
75%
100%
Mocking for PR validation
87%
87%
Remote state backend present
100%
100%
State encryption enabled
100%
100%
State locking configured
100%
100%
Terraform version pinned correctly
100%
100%
Provider version pinned correctly
100%
100%
Secrets remediation mentions write-only or Secrets Manager
83%
100%
Secrets remediation explains state risk
100%
100%
Security scanning in CI
20%
100%
No .tfvars files committed
60%
100%
4596913
Table of Contents
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.