terraform

Generate and harden Terraform modules and environment repositories with standards and CI guardrails.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill terraform-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terraform
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/terraform
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill terraform-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing production-grade Terraform from scratch is error-prone: inconsistent layouts, missing version constraints, unsafe secret handling, and absent validation checks lead to fragile infrastructure code. This Skill scaffolds and reviews Terraform modules and environment roots against documented standards. ## Core Features & Use Cases - Scaffolding: Generates module-library or environment-roots layouts with main.tf, variables.tf, outputs.tf, versions.tf, examples, and documentation. - Hardening & Review: Enforces provider version constraints, remote state and locking guidance, secret-handling rules (write-only args, ephemeral values, sensitive flags), and security guardrails. - Quality Gates: Adds terraform fmt, validate, tflint, checkov/tfsec, lockfile drift checks, Makefile targets, and CI hooks. - Use Case: Ask it to scaffold a reusable networking module with dev/stage/prod environment roots, S3 remote state with lockfile-based locking, and a CI pipeline that fails on lock drift. ## Quick Start Use the terraform skill to scaffold a production-grade Terraform module with remote state, examples, and CI validation for my project.

Frequently Asked Questions about terraform

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

FAQPage Schema
How do I scaffold a production-grade Terraform module?

Invoke the terraform skill with your module name, target Terraform version, providers, and remote state choice. It generates a module-library or environment-roots layout with variables, outputs, validation blocks, examples, documentation, and CI quality gates.

How should Terraform handle secrets without storing them in state?

Prefer avoiding secrets in Terraform entirely. If required, use write-only resource arguments on Terraform 1.11+, ephemeral values on 1.10+, or fall back to sensitive = true with hardened remote state and a secret manager.

Does the skill support remote state backends like S3 or Azure?

Yes. It configures remote state with partial backend configuration and identity-based credentials. For S3 it prefers lockfile-based locking via use_lockfile; for azurerm it relies on native Blob lease locking.

What Terraform version constraints should modules use?

Child modules declare minimum supported provider versions only, while root modules add explicit upper bounds. The default Terraform constraint is >= 1.10.0, < 2.0.0, and lock files pin exact provider versions in root configurations.

When should I not use Terraform for deployments?

Do not implement application deployment workflows in Terraform; use GitOps or CI/CD for application rollout. Terraform is scoped to infrastructure and platform IaC such as networking, IAM, compute, Kubernetes infrastructure, and storage.