terraform-engineer

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.

Quality

92%

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

Quality

Content

92%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.

Well-structured, actionable body with a strong sequenced workflow, validation/feedback loops, and clean progressive disclosure to real reference files. Only minor conciseness trim needed in the redundant intro sentence.

Suggestions

Remove or shorten the opening 'Senior Terraform engineer specializing in...' sentence since it duplicates the frontmatter description.

Consider noting the '.tf' extension and 'IaC' synonym in the description for stronger trigger coverage.

Dimension	Reasoning	Score
Conciseness	Mostly lean and efficient with concrete commands and tight HCL, but the opening 'Senior Terraform engineer specializing in...' line largely restates the description and could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready commands (terraform fmt/validate/plan/apply, tflint, state rm/import, init) and complete executable HCL examples for module structure, S3 backend, and provider pinning covering the common cases.	5 / 5
Workflow Clarity	A clearly sequenced 7-step workflow with explicit validation checkpoints (step 5 re-run-until-clean loop), an approval gate for destructive changes, and a dedicated error-recovery section with feedback loops back to step 5.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview; the Reference Guide table signals five real one-level-deep reference files (module-patterns, state-management, providers, testing, best-practices) with explicit 'Load When' navigation cues.	5 / 5
	Total	19 / 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, specific description that clearly states capabilities and explicit use-conditions with concrete trigger phrases. Minor keyword gaps (IaC synonym, .tf extension) keep trigger_term_quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across several domains — 'create reusable modules, manage module versioning', 'migrate backends, import existing resources, resolve state conflicts', 'provider configuration', 'multi-environment workflows', and 'infrastructure testing' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (implementing IaC, module development, state management, provider config, multi-env workflows, testing) and when ('Use when implementing...', 'Invoke for...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords (Terraform, infrastructure as code, AWS/Azure/GCP, module, state, provider) but missing common synonyms like 'IaC' and the '.tf' file extension that users would naturally say.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Terraform-specific niche with distinct triggers across AWS/Azure/GCP; conflict risk with adjacent devops/cloud skills is minimal given the tool-specific framing.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Path: skills/terraform-engineer/SKILL.md
Commit: 882ef55

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