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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

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

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.

Highly actionable body rich in executable HCL/YAML/bash and concrete checklists, but it is over-long for SKILL.md: reference files are orphaned while their content is inlined, and destructive workflows (auto-approve apply) lack validation checkpoints. Tightening and routing detail into the existing references would lift both conciseness and progressive disclosure.

Suggestions

Move the Module Design Patterns, State Management Decision Tree, and Provider Configuration sections into references/module-patterns.md and references/state-management.md, linking to them from the body so SKILL.md stays an overview.

Add an explicit validation checkpoint before destructive applies — e.g. gate 'terraform apply -auto-approve' behind a reviewed plan ('terraform plan -out=tfplan', review, then 'terraform apply tfplan') or a stated approval step.

Trim flavor prose (e.g. 'doesn't break at 3 AM') and consolidate the review/module/security checklists to reduce token weight without losing the concrete actions.

Dimension	Reasoning	Score
Conciseness	The body is largely actionable checklists and code with little conceptual over-explanation, but at ~740 lines it inlines substantial reference material (module patterns, state decision tree, provider configs, Terragrunt/OpenTofu/Infracost sections) that could be tightened or offloaded, and includes minor flavor ('doesn't break at 3 AM').	3 / 5
Actionability	Dense with copy-paste-ready, executable HCL, bash, and YAML plus concrete severity-rated checklists and real referenced scripts, covering the common cases comprehensively.	5 / 5
Workflow Clarity	The three slash-command workflows are numbered and sequenced, but destructive/batch operations lack validation checkpoints — most notably 'terraform apply -auto-approve' runs with no explicit validate-then-apply gate — which caps workflow clarity per the destructive-operations rule.	3 / 5
Progressive Disclosure	Section structure is clear and the two scripts are well-signaled and real, but references/module-patterns.md and references/state-management.md exist yet are never linked from the body, while their subject matter is inlined as full sections — content that should be separate is inline and references are not signaled.	3 / 5
	Total	14 / 20 Passed

Description

92%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, third-person description that concretely states both what the skill covers and when to invoke it, with comprehensive capability listing and clear trigger guidance. The only gap is a few natural trigger synonyms (.tf, HCL) that would round out keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows' — giving comprehensive coverage of the skill's actions.	5 / 5
Completeness	Explicitly answers both 'what' (the Covers... capabilities) and 'when' with a concrete 'Use when: user wants to...' clause listing distinct trigger scenarios.	5 / 5
Trigger Term Quality	Good natural trigger phrases ('design Terraform modules', 'manage state backends', 'review Terraform security', 'multi-region deployments'), but common variations like '.tf files', 'HCL', and 'Terraform state' as a bare phrase are absent, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Clear Terraform/IaC niche with distinct triggers; the broadest phrase ('IaC best practices') is anchored to Terraform, so overlap with unrelated skills is minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 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

	Total	15 / 16 Passed

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

Reviewed: ~3 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.