Use the Infrastructure as code pack
Install the Infrastructure as code pack, run its first task, and follow a typical session step by step.
Terraform you can hand to another team and plans you can trust before apply: reusable modules with secure defaults, and a plan review that catches destroys, data loss, access widening and drift.
Reach for it when: You need new infrastructure as a reusable Terraform module, or you have a plan in front of you and want to know whether it is safe to apply.
1. Install it
npx skilldrop-cli install --pack infra-as-code # Claude Code, your user folder
npx skilldrop-cli install --pack infra-as-code --project # Claude Code, this repo
npx skilldrop-cli install --pack infra-as-code --ide cursor # or kiro, codex, antigravity, copilot
npx skilldrop-cli install --pack infra-as-code --local # this repo, hidden from git
In Claude Code you can also add the marketplace once (/plugin marketplace add sananthanarayan/skilldrop) and run /plugin install infra-as-code@skilldrop.
It brings core with it, so the shared skills are there too.
2. Run the first task: write a module, then review its plan before the first apply
Before you start:
- A Terraform project or a described piece of infrastructure
- Terraform installed locally if you want to validate and plan the result
Paste this into your agent:
Write a Terraform module for an S3 bucket that stores our access logs for a year. Several teams will call it. Then, once I've run terraform plan on the example, review the plan before I apply.
How to tell it worked: terraform-module writes versions.tf, variables.tf, main.tf, outputs.tf, a basic example and a README with inputs and outputs tables, with encryption on and public access off by default. terraform-plan-review returns SAFE TO APPLY, APPLY WITH CARE or DO NOT APPLY with every destroy and replace named.
If nothing happens: If terraform validate fails, paste the error back and ask terraform-module to fix that file. If terraform-plan-review does not activate, ask for it by name ("use terraform-plan-review") and give it the output of terraform show -json tfplan.
3. A typical session
Bring:
- what the infrastructure is for and which cloud it runs on
- who will call the module
- the output of terraform plan, ideally terraform show -json tfplan
- one sentence on what the change is meant to do
A session takes about 20 to 45 minutes.
terraform-module: Describe the need, the cloud and the callers. You get: A module with versions.tf, typed and validated variables, secure defaults, a tags variable, a basic example, a README, and the commands to check it.terraform-plan-review: Run terraform plan, save it with terraform show -json, and hand it over with the intent of the change. You get: Counts, every destroy and replace with its cause, stateful and access changes, drift, out-of-scope changes and a verdict. You decide: Apply, apply after the listed checks, or fix the code and re-plan.doc-critique: Optionally, run it on the module README before you publish the module to other teams. You get: Severity-tagged findings on gaps and unclear inputs, with a fix for each.
You end with: A reusable module with safe defaults, and a reviewed plan with a clear apply decision.
Next
- Every skill in the Infrastructure as code pack: what each one makes, needs and hands off to
- The pack's page, with one-click copy for every command
- Upgrade installed skills when a new version ships