Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/generating-infrastructure-as-code

@820dfc8
Run it yourself

Execute use when generating infrastructure as code configurations. Trigger with phrases like "create Terraform config", "generate CloudFormation template", "write Pulumi code", or "IaC for AWS/GCP/Azure". Produces production-ready code for Terraform, CloudFormation, Pulumi, ARM templates, and CDK across multiple cloud providers.

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/generating-infrastructure-as-code

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈91 tokens for metadata: the name and description. ≈988 when used: this file. ≈1.8k more on demand in 4 files.

Description uses 4.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈366 characters, or 4.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Generating Infrastructure as Code

Overview

Generate production-ready infrastructure as code for Terraform, CloudFormation, Pulumi, ARM templates, and AWS CDK. Produce modular, well-structured configurations with proper variable definitions, outputs, remote state management, and deployment guidance for AWS, GCP, and Azure cloud stacks.

Prerequisites

  • Target cloud provider CLI installed and authenticated (aws, gcloud, az)
  • IaC tool installed: Terraform 1.0+, Pulumi 3+, AWS CDK, or relevant SDK
  • Cloud credentials configured with permissions to create the target resources
  • Understanding of the desired infrastructure architecture (compute, networking, storage, database)
  • Version control repository for storing IaC configurations

Instructions

  1. Identify the IaC tool and cloud provider based on the project requirements and existing codebase
  2. Scan the project for existing IaC files to understand current patterns and conventions
  3. Define the modular file structure: separate files for providers, networking, compute, storage, and databases
  4. Generate the provider configuration with version pinning and remote backend for state storage
  5. Define input variables with types, descriptions, defaults, and validation rules for all configurable values
  6. Write resource definitions following cloud provider best practices: encryption enabled, logging configured, least-privilege IAM
  7. Add outputs for resource identifiers, endpoints, and connection strings needed by other modules or applications
  8. Configure remote state backend: S3 + DynamoDB for Terraform, Pulumi Cloud, or CloudFormation stack exports
  9. Create environment-specific variable files (terraform.tfvars, dev.tfvars, prod.tfvars) for multi-environment deployment
  10. Validate with terraform validate, terraform plan, or equivalent tool-specific linting

Output

  • IaC configuration files organized by resource type or module
  • Variable definition files with documented inputs and sensible defaults
  • Output definitions for cross-module references and application configuration
  • Backend configuration for remote state storage
  • Environment-specific variable files for dev, staging, and production
  • Deployment instructions with prerequisite setup and apply commands

Error Handling

Error Cause Solution
Invalid HCL syntax Malformed Terraform configuration Run terraform validate to identify the error; check bracket matching and attribute syntax
Unable to authenticate with cloud provider Missing or expired credentials Run aws configure, gcloud auth login, or az login to refresh credentials
Resource already exists Trying to create a resource that exists outside of IaC management Use terraform import to bring the existing resource under management
Error acquiring state lock Another process holding the state lock Wait for the other process to finish; use terraform force-unlock <ID> if the lock is stale
Dependency cycle detected Resources referencing each other circularly Refactor to remove the cycle; use data sources or depends_on to establish explicit ordering

Examples

  • "Generate Terraform for a production VPC on AWS with public/private subnets across 3 AZs, NAT gateways, VPC flow logs, and an EKS cluster."
  • "Create a CloudFormation template for an S3 bucket with versioning, server-side encryption (KMS), public access block, and lifecycle rules."
  • "Write Pulumi TypeScript code for a GCP Cloud Run service with a custom domain, Cloud SQL database, and Secret Manager integration."

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides functionality for generating Infrastructure as Code (IaC) and includes a utility script that creates and marks shell scripts as executable. It also involves scanning existing project files, which introduces a potential surface for indirect prompt injection.

  • Socket2mo

    1 alert: gptAnomaly

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
1.24.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "devops",
  "terraform",
  "infrastructure-as"
]
All 9 allowed tools
ReadWriteEditGrepGlobBash(terraform:*)Bash(aws:*)Bash(gcloud:*)Bash(az:*)
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/generating-infrastructure-as-code