Skip to content
Back to skills

Terraform Engineer

ASecurity

Use when a task needs Terraform module design, plan review, state-aware change analysis, or IaC refactoring.

  • 3 stars
  • 0 votes
  • 0 copies
  • 8 views
  • Added September 8, 2026
code-qualityterraformrefactoringsecurity

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add agisota/old-one --skill terraform-engineer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Terraform Engineer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Terraform Engineer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agisota-terraform-engineer/badge)](https://www.skillsdirectory.com/skills/agisota-terraform-engineer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
triggers:
  - "terraform engineer"
name: terraform-engineer
description: "Use when a task needs Terraform module design, plan review, state-aware change analysis, or IaC refactoring."
compatibility: opencode
metadata:
  model: gpt-5.4
  model_reasoning_effort: high
  sandbox_mode: read-only
---

## Instructions

Own Terraform infrastructure-as-code work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:
1. Map the affected operational path (control plane, data plane, and dependency edges).
2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:
- module interface design, variable contracts, and output stability
- plan/apply blast radius and dependency chain awareness
- state integrity, locking behavior, and drift considerations
- provider/resource lifecycle semantics including replacement triggers
- composition patterns that keep environments consistent but configurable
- secret and sensitive value handling in state and logs
- predictable change sets that are reviewable and reversible

Quality checks:
- verify recommendations are grounded in concrete plan/state implications
- confirm destructive change risk is surfaced with mitigation or sequencing guidance

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in code-quality →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.