Skip to content
SkillModel-led1,626 tokens in use

Terraform Engineer

Terraform modules, remote state and provider setup for AWS, Azure and GCP, with a validate, plan and approve loop before any apply.

12,471 stars on the repository MIT LicenseJeffallan/claude-skills · skills/terraform-engineer
/plugin install fullstack-dev-skills@fullstack-dev-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Terraform Engineer costs

64tokens idle
1,626tokens in use
15,246tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter15/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity36
  • Momentum40

Terraform Engineer gives the agent a working method for infrastructure as code. It analyzes the existing setup, designs reusable modules, configures remote state with locking and encryption, and runs format, validate, lint and test checks before it plans.

It ends with a plan summary that highlights creates, updates and destructive changes. The agent applies only after you confirm, and it refuses to apply destructive changes you have not accepted.

What You Get

  • A seven-step workflow from analysis to an approved apply
  • Module structure with typed, validated variables, described outputs and the standard file layout
  • Remote backend configuration with native S3 locking and encryption
  • Recovery steps for validation failures, state drift, provider auth errors and ordering problems
  • Five reference files for modules, state, providers, testing and best practices

Common Use Cases

  • Writing a reusable module with input validation and versioning
  • Migrating a backend or importing existing resources into state
  • Adding native terraform test files for a module
  • Setting up provider pinning and a lock file for several clouds

What Makes It Unique

The skill puts an approval gate into the workflow. The agent must present a plan summary and wait for your confirmation, and any command that writes state (refresh-only apply, import, state mv, state rm) needs approval first. It also names deprecated constructs to avoid in new code, such as terraform refresh, DynamoDB state locking and tfsec, and points to current replacements like use_lockfile, moved and import blocks, and Trivy.

Under The Hood

The skill loads SKILL.md and pulls in one reference file at a time when the task matches its topic. It tells the agent to run shell commands: terraform fmt, validate, plan, test and apply, plus tflint and trivy or checkov when installed. The plan is written to a plan file on disk and applied only after you approve it. The commands read cloud credentials and provider settings from your environment, can change real infrastructure on apply, and can modify state files. The skill tells the agent never to print state, because state can hold sensitive values. The skill itself contains no scripts.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers