Back to catalog
Human reviewedDevelopment

Skill dossier

terraform-engineer

Source declaration

Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.

The author's original description, preserved in English. It describes intent, not verified performance.

Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

Guides Terraform infrastructure-as-code work on AWS, Azure and GCP, from module design and remote state to validation, plan review and approval-gated apply.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Designs composable, validated modules with clear interfaces.
  • Configures remote backends with locking and encryption, and pins provider versions.
  • Runs terraform fmt, validate and tflint, then produces a plan summary highlighting destructive actions.
  • Applies a plan only after explicit user approval.

Limitations & scope

  • Needs Terraform, tflint and valid cloud credentials installed locally.
  • Examples are AWS-centric, with Azure and GCP covered mainly through provider configuration.
  • Cloud costs and the actual outcome of apply are not verified here.

Relevant for

  • Infrastructure and platform engineers
  • Teams standardizing reusable Terraform modules
  • Engineers migrating state backends

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
49.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/terraform-engineer/references/best-practices.mdReference12.3 KB
skills/terraform-engineer/references/module-patterns.mdReference5.8 KB
skills/terraform-engineer/references/providers.mdReference8.9 KB
skills/terraform-engineer/references/state-management.mdReference7.7 KB
skills/terraform-engineer/references/testing.mdReference9.6 KB
skills/terraform-engineer/SKILL.mdInstruction5.6 KB

SKILL.md frontmatter

{
  "name": "terraform-engineer",
  "description": "Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "infrastructure",
    "triggers": "Terraform, infrastructure as code, IaC, terraform module, terraform state, AWS provider, Azure provider, GCP provider, terraform plan, terraform apply",
    "role": "specialist",
    "scope": "implementation",
    "output-format": "code",
    "related-skills": "cloud-architect, devops-engineer, kubernetes-specialist"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Analyze infrastructure

    Review requirements, existing code and cloud platforms.

  2. 02
    Action

    Validate configuration

    Run terraform fmt, terraform validate and tflint, fixing errors until all checks pass.

  3. 03
    Decision

    Gate apply on approval

    Present the plan summary and apply only after explicit confirmation; refuse if destructive changes are not accepted.

  4. 04
    Output

    Deliver Terraform code

    Provide module structure, backend and provider configuration, example tfvars and design notes.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

43 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

27 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 27 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

3 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

13 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 13 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Use least-privilege cloud credentials and read the plan summary before approving any terraform apply, especially state-modifying commands.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/terraform-engineer # .claude/skills/terraform-engineer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/terraform-engineer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Confirm SKILL.md is discoverable at the destination, then ask Claude Code to use terraform-engineer on a small task.

Prerequisites

  • Needs Terraform, tflint and valid cloud credentials installed locally.
  • Examples are AWS-centric, with Azure and GCP covered mainly through provider configuration.
  • Cloud costs and the actual outcome of apply are not verified here.

Example prompts

Representative task

Use the terraform-engineer skill to create a reusable S3 bucket module with input validation, configure an encrypted S3 backend with DynamoDB locking, and show me the plan summary before applying anything.

Inspect before use

Read the terraform-engineer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/terraform-engineer/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Approval gate: apply is refused without explicit confirmation or if destructive changes are not accepted.
  • Includes an error recovery section for drift, auth and dependency failures.

Considerations

  • Suggests commands such as terraform state rm and refresh that can alter state.
  • Real infrastructure changes depend on credentials the agent can reach.
Research conclusion

A careful IaC skill whose approval gate and validation loop suit teams that apply Terraform to real environments.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/terraform-engineer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.