terraform

Automate Terraform and Terragrunt infrastructure code following HashiCorp best practices.

13|1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/mauromedda/agent-toolkit --skill terraform-mauromedda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform
Source: https://github.com/mauromedda/agent-toolkit/tree/main/skills/terraform
Command: npx skills add https://github.com/mauromedda/agent-toolkit --skill terraform-mauromedda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Terraform and Terragrunt configurations often drift from best practices, leading to duplication, insecure state, and brittle deployments. This skill enforces HashiCorp guidance for modular, auditable, and secure infrastructure code.

Core Features & Use Cases

  • DRY design with Terragrunt for multi-environment deployments
  • Secure, remote state management with encrypted backends
  • Consistent naming, input validation, and module usage
  • Use Case: Standardize a multi-account AWS setup with centralized backend and validated modules.

Quick Start

Install Terraform and Terragrunt, set up a remote backend, and apply a minimal environment configuration to provision example resources.

Frequently Asked Questions about terraform

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage remote state securely across multiple Terraform environments?

Secure Terraform remote state across environments by configuring encrypted backends and using Terragrunt for DRY multi-environment deployments, ensuring auditable infrastructure code.

What is the best way to structure infrastructure-as-code for a multi-account AWS setup?

Structure infrastructure-as-code for multi-account AWS setups by standardizing centralized remote backends, enforcing consistent naming conventions, and utilizing validated modules.

How do I avoid storing secrets in state when provisioning cloud infrastructure with Terraform?

Avoid storing secrets in Terraform state by following HashiCorp best practices for input validation and secure state management during cloud provisioning scenarios.

Does Terragrunt work with Terraform to enforce DRY module usage?

Terragrunt works with Terraform to enforce DRY design for multi-environment deployments, applying HashiCorp guidance for modular, auditable, and secure infrastructure code.

Why does my Terraform infrastructure code drift from HashiCorp best practices?

Terraform infrastructure code drifts from best practices due to configuration duplication, insecure state management, and brittle deployments lacking strict input validation and naming conventions.