terraform-iac
Deep Terraform/IaC workflow—module boundaries, state, workspaces, plan/apply safety, drift, secrets, CI integration, and team governance. Use when building infra as code, refactoring modules, or debugging state issues.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/clawkk/terraform-iacWhat This Skill Does
The terraform-iac skill provides a professional-grade framework for managing Infrastructure as Code (IaC) workflows. It focuses on the most critical and complex aspects of Terraform: state management, module design, security, and team-based CI/CD orchestration. Rather than just writing syntax, this skill helps you architect your infrastructure to be modular, reproducible, and resilient to failure. It enforces industry-standard patterns like the 'Live vs. Modules' directory structure, secure state backend configuration, and robust plan-and-apply safety protocols. Whether you are building a greenfield environment or untangling a legacy state file, this skill acts as an infrastructure architect, ensuring that your blast radius is controlled and your team's workflow is automated through policy-as-code and OIDC-based authentication.
Installation
You can install the skill by running the following command in your terminal:
clawhub install openclaw/skills/skills/clawkk/terraform-iac
Use Cases
- Greenfield Infrastructure: Setting up a scalable, multi-environment architecture that supports future growth.
- Refactoring Legacy Code: Migrating monolith modules into granular, reusable components without destroying production infrastructure, utilizing
movedblocks. - Incident Response: Diagnosing and resolving state locking issues, fixing resource drift, and recovering from failed apply operations.
- CI/CD Hardening: Implementing secure Plan-on-PR workflows, OPA/Sentinel policy integration, and managing secrets via provider-native solutions like HashiCorp Vault.
Example Prompts
- "I need to refactor our current monolithic VPC module into smaller, environment-agnostic components. Can you help me plan the directory structure and the necessary
movedblocks to avoid downtime?" - "We are seeing consistent drift in our S3 bucket configurations across production. How can I audit the existing state and configure a CI pipeline to prevent manual drift in the future?"
- "Help me design a secure workflow for multi-account AWS deployments where we need to separate state files per environment and use OIDC instead of long-lived access keys."
Tips & Limitations
- Safety First: Always use
terraform planand output it to a file before applying. The skill emphasizes peer reviews for any plan targeting production. - State Sensitivity: Remember that Terraform state often contains raw secrets. Ensure your backend supports encryption at rest and strict IAM policies.
- Blast Radius: Avoid 'mega-modules' that encompass the entire infrastructure. Smaller, single-responsibility modules are easier to test and version-control.
- Limitation: This skill is an architectural guide and implementation assistant; it requires that you have the appropriate cloud provider permissions configured. It cannot override cloud-provider-level permission errors.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-clawkk-terraform-iac": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, external-api, code-execution
Related Skills
data-move
Deep data migration workflow—scope, mapping, validation, batching and ordering, dual-write and cutover, rollback, and reconciliation. Use when moving tenants, bulk backfills, or changing stores without losing trust in data correctness.
data-model
Deep data modeling workflow—grain, facts and dimensions, keys, slowly changing dimensions, normalization trade-offs, and analytics query patterns. Use when designing warehouse/analytics models or reviewing star/snowflake schemas.
guard
Deep AI safety guardrails workflow—policy definition, input/output filtering, monitoring, escalation, and false-positive handling. Use when reducing harmful outputs, misuse, or policy violations in LLM products.
prompts
Deep prompt engineering workflow—task spec, constraints, examples, evaluation sets, iteration protocol, regression testing, and safety alignment. Use when improving LLM outputs, shipping prompt changes, or building reusable prompt templates.
cost-opt
Cloud cost review: rightsizing, reservations, waste. Use when reducing infra spend.