Skip to content
cccskills
FreePublished on GitHub

building-terraform-modules

Generate reusable Terraform modules for AWS, GCP, or Azure resources, with inputs, outputs, validation rules, examples, and documentation. It also applies security defaults such as encryption and restricted public access.

OriginalShow the original description

Execute this skill empowers AI assistant to build reusable terraform modules based on user specifications. it leverages the terraform-module-builder plugin to generate production-ready, well-documented terraform module code, incorporating best practices for sec... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

jeremylongshore/tons-of-skills-marketplace2,884 stars(GitHub 2,884 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Creating a configurable AWS VPC module
  • Building a GCP Cloud Run module
  • Packaging secure S3 bucket settings as a reusable module

Files included (5)

  • SKILL.md4.3 KB
  • assets/README.md451 B
  • assets/validation_rules.json3.6 KB
  • references/README.md67 B
  • scripts/README.md507 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Building Terraform Modules

Overview

Build reusable, production-ready Terraform modules with proper variable definitions, outputs, validation rules, documentation, and examples. Generate modules following HashiCorp's standard module structure for AWS, GCP, and Azure resources with security best practices, tagging conventions, and lifecycle management.

Prerequisites

  • Terraform 1.0+ installed (terraform version)
  • Cloud provider credentials configured for the target platform
  • Understanding of the infrastructure resources the module will manage
  • Familiarity with HCL syntax and Terraform module conventions
  • terraform-docs installed for automated documentation generation (optional)

Instructions

  1. Define the module scope: determine which cloud resources the module manages and its input/output contract
  2. Create the standard module file structure: main.tf, variables.tf, outputs.tf, versions.tf, locals.tf
  3. Write versions.tf with required_version and required_providers blocks pinned to stable versions
  4. Define input variables in variables.tf with descriptions, types, defaults, and validation rules
  5. Implement resources in main.tf using variables for all configurable values; use locals for computed values
  6. Add meaningful outputs in outputs.tf for resource IDs, ARNs, endpoints, and connection strings
  7. Implement security defaults: encryption enabled, public access blocked, least-privilege IAM, logging enabled
  8. Create an examples/ directory with at least one complete usage example showing module invocation
  9. Generate documentation with terraform-docs markdown table . > README.md
  10. Validate the module with terraform init && terraform validate and test with terraform plan using the example

Output

  • Module files: main.tf, variables.tf, outputs.tf, versions.tf, locals.tf
  • Example usage in examples/basic/main.tf with realistic variable values
  • Auto-generated README.md with inputs, outputs, and usage documentation
  • .terraform-docs.yml configuration for documentation generation
  • Optional: test files using Terratest or terraform test (HCL-based)

Error Handling

ErrorCauseSolution
variable validation failedInput value does not meet validation ruleCheck the validation block in variables.tf; adjust the value or the validation regex
provider not foundMissing or wrong provider source in versions.tfAdd the provider to required_providers with correct source and version constraint
circular dependencyResources referencing each other in a loopRefactor to break the cycle; use depends_on or separate into sub-modules
output references undeclared resourceTypo in resource name or resource removedVerify resource names in main.tf match output references exactly
module source not foundIncorrect module path or registry referenceVerify the source path is relative (e.g., ./modules/vpc) or a valid registry address

Examples

  • "Build a Terraform module for an AWS VPC with configurable CIDR, public/private subnets across 3 AZs, NAT gateway, and flow logs."
  • "Create a GCP Cloud Run module with custom domain, IAM bindings, and auto-scaling configuration as input variables."
  • "Generate a Terraform module for an S3 bucket with versioning, encryption, lifecycle rules, and access logging, with all settings as optional variables with secure defaults."

Resources

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 29, 2026

Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 29, 2026

Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 29, 2026

Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 29, 2026

Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 29, 2026

Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 29, 2026

See all skills by jeremylongshore

Report a problem with this skill