Name: terraform-patterns
Rating: 63.2 (1 reviews)
Author: alirezarezvani

terraform-patterns

Terraform infrastructure-as-code agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Covers module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows. Use when: user wants to design Terraform modules, manage state backends, review Terraform security, implement multi-region deployments, or follow IaC best practices.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/terraform-patterns/SKILL.md

The canonical home for this skill is terraform-patterns in alirezarezvani/claude-skills

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, code-rich Terraform skill body that suffers from monolithic length, redundant security coverage, and broken script references to files absent from the bundle. Workflow clarity is capped by missing validation feedback loops around destructive operations.

Suggestions

Split the secondary topics (OpenTofu Compatibility, Infracost Integration, Terragrunt Patterns, Multi-Cloud Provider Configuration, CI/CD Integration Patterns) into reference files under references/ and keep SKILL.md as a concise overview that links to them one level deep.

Either ship the referenced scripts (tf_module_analyzer.py, tf_security_scanner.py, convert.sh) in a scripts/ directory or remove the run-instructions that depend on them, so the body never points to nonexistent bundle files.

Add explicit validation feedback loops to the destructive workflows, e.g. after terraform import run terraform plan and only proceed when the diff is clean; before terraform apply -auto-approve require a passing plan and state backup.

Dimension	Reasoning	Score
Conciseness	The 741-line body is mostly concrete checklists, code, and decision trees, but it is monolithic, repeats security checks across the review, security, and proactive-triggers sections, and includes tool-intro prose ("OpenTofu is an open-source fork of Terraform...", "Infracost estimates cloud costs...") that explains concepts Claude already knows.	3 / 5
Actionability	Provides fully executable, copy-paste-ready guidance throughout: complete HCL provider/version blocks, GitHub Actions plan/apply and drift-detection YAML, terraform CLI and import commands, and concrete severity/fix tables covering the common cases.	5 / 5
Workflow Clarity	The /terraform:review, :module, and :security workflows are clearly numbered with checklists, but there are no explicit validate->fix->retry feedback loops, and destructive or batch operations (terraform apply -auto-approve, terraform state mv/rm, import) lack structured validation checkpoints, which caps the score.	3 / 5
Progressive Disclosure	Internal section structure is good (clear headers, tables, code fences), but nearly everything is inlined into one massive file and the body instructs running scripts/tf_module_analyzer.py, scripts/tf_security_scanner.py, and scripts/convert.sh that do not exist in the bundle, so the references are broken.	3 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, complete description that explicitly states both capabilities and trigger conditions with concrete phrases. It is held back from perfection by a topic-oriented coverage list and the omission of common synonyms like .tf and HCL.

Dimension	Reasoning	Score
Specificity	Lists several specific coverage areas ("module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows") and concrete verbs ("design Terraform modules, manage state backends, review Terraform security, implement multi-region deployments"), but the main coverage list is topic-oriented rather than crisp discrete actions, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both what ("Covers module design patterns, state management strategies...") and when ("Use when: user wants to design Terraform modules, manage state backends...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with natural phrases ("Terraform modules", "state backends", "Terraform security", "multi-region deployments", "IaC best practices"), but misses common synonyms and extensions users say like ".tf", "HCL", or "terraform plan/apply".	4 / 5
Distinctiveness Conflict Risk	Clear Terraform infrastructure-as-code niche with distinct triggers and minimal conflict risk; the "plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw" prefix adds mild meta-noise but does not blur the distinct niche.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (741 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 12 missing	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/terraform-patterns/SKILL.md
Commit: 19392f7

Reviewed: ~4 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.