Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/terraform-skill
Terraform infrastructure as code best practices
Passed 20 of 22 test cases with the skill, and 18 of 22 without it.
3 fixed17 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Terraform 1.9+, we need to enforce that if `var.environment` equals `'prod'`, the `var.backup_retention_days` value must be at least 7. Where and how should this rule be defined?
| Checked | Without skill | With skill |
|---|---|---|
| Defines a validation condition referencing both var.environment and var.backup_retention_days inside a variable block | Missed | Passed |
The instructions your model reads when the skill loads.
Comprehensive Terraform and OpenTofu guidance covering testing, modules, CI/CD, and production patterns. Based on terraform-best-practices.com and enterprise experience.
Activate this skill when:
Don't use this skill for:
Module Hierarchy:
| Type | When to Use | Scope |
|---|---|---|
| Resource Module | Single logical group of connected resources | VPC + subnets, Security group + rules |
| Infrastructure Module | Collection of resource modules for a purpose | Multiple resource modules in one region/account |
| Composition | Complete infrastructure | Spans multiple regions/accounts |
Hierarchy: Resource → Resource Module → Infrastructure Module → Composition
Directory Structure:
environments/ # Environment-specific configurations
├── prod/
├── staging/
└── dev/
test cases passed, vs 18 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.