terraform-module-library

Creates reusable Terraform modules for AWS, Azure, and GCP infrastructure provisioning with a standard structure.

4|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill terraform-module-library-ai-foundry-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform-module-library
Source: https://github.com/AI-Foundry-Core/ril-agents/tree/main/plugins/cloud-infrastructure/skills/terraform-module-library
Command: npx skills add https://github.com/AI-Foundry-Core/ril-agents --skill terraform-module-library-ai-foundry-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

Core Features & Use Cases

  • Standard module layout for consistent provisioning across clouds (main.tf, variables.tf, outputs.tf, versions.tf, README.md)
  • Multi-cloud patterns enabling reuse across AWS, Azure, and GCP
  • Documentation and testing guidance with examples and recommended testing approaches
  • Use Case: Create a common VPC module and reuse across clouds to accelerate delivery and enforce standards

Quick Start

Initialize and reference a multi-cloud Terraform module library to bootstrap a new infrastructure project.

Frequently Asked Questions about terraform-module-library

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

FAQPage Schema
How do I create reusable Terraform modules for multi-cloud infrastructure?

To create reusable Terraform modules for multi-cloud infrastructure, structure your project with a standard layout including main.tf, variables.tf, outputs.tf, versions.tf, README.md, examples, and tests to enforce consistent architecture across AWS, Azure, and GCP.

What files are required for a standard Terraform module structure?

A standard Terraform module structure requires main.tf, variables.tf, outputs.tf, versions.tf, and README.md, alongside examples and tests. This layout standardizes module architecture, naming, inputs, and outputs for consistent team provisioning.

Does this approach work for standardizing provisioning across AWS, Azure, and GCP?

Yes, this approach works for standardizing provisioning across AWS, Azure, and GCP by applying multi-cloud patterns within the Terraform module architecture, ensuring consistent naming, inputs, and outputs across different cloud teams.

When do I need to use a modular infrastructure-as-code design pattern?

You need to use a modular infrastructure-as-code design pattern when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components to accelerate delivery and enforce standards across multiple teams.

What's the best way to document and test Terraform modules for team reuse?

The best way to document and test Terraform modules for team reuse is following the standard structure by including a README.md for documentation and dedicated examples and tests directories to validate and demonstrate recommended testing approaches.