Infrastructure as Code
v1.0.0Define and manage cloud infrastructure with code. Use when writing Terraform, CloudFormation, or Pulumi configs, managing state, planning deployments, setting up networking/compute/storage resources, or debugging infrastructure drift.
⭐ 1· 3.1k·11 current·13 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the content: the SKILL.md contains Terraform, CloudFormation, and Pulumi guidance and the declared required binaries (terraform, aws, pulumi) are appropriate and expected for this purpose.
Instruction Scope
Instructions stay within IaC tasks (init, plan, apply, module patterns, examples). There is no guidance to read unrelated system files or exfiltrate data. The doc does show example use of environment-driven secrets (TF_VAR_db_password) and standard provider variables, which is expected for IaC.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded by the skill itself.
Credentials
The skill declares no required env vars, which is reasonable for documentation. The instructions do reference standard IaC environment usage (e.g., TF_VAR_db_password and the implicit need for cloud credentials such as AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY when running provider commands). That is expected, but users should be aware the agent will need cloud credentials in its environment to actually run Terraform/AWS/Pulumi commands.
Persistence & Privilege
always is false and the skill does not request persistent system-level privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with any other concerning flags.
Assessment
This skill is a documentation/assistant for IaC and is internally consistent. Before using it: be aware that actually running terraform/aws/pulumi commands will require cloud credentials (e.g., AWS keys) in the agent environment — grant only least-privilege IAM credentials. Prefer running terraform plan and reviewing diffs before apply; avoid running apply against production without human approval. Keep secrets out of committed files (use remote state and secret management), inspect any generated or recommended code before executing it, and consider limiting autonomous agent actions or requiring explicit user confirmation for destructive operations.Like a lobster shell, security has layers — review code before you run it.
latestvk975xexf4ktwh98g71h8n1wxqd80f87c
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🏗️ Clawdis
OSLinux · macOS · Windows
Any binterraform, aws, pulumi