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.
94
92%
Does it follow best practices?
Impact
95%
1.07xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope around Terraform infrastructure-as-code workflows. It provides explicit trigger guidance ('Use when...', 'Invoke for...'), lists concrete actions across multiple sub-domains, and includes natural keywords users would use. The description is concise yet comprehensive, making it easy for Claude to distinguish from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: module development, module versioning, state management, backend migration, resource importing, state conflict resolution, provider configuration, multi-environment workflows, and infrastructure testing. | 3 / 3 |
Completeness | Explicitly answers both 'what' (module development, state management, provider configuration, testing, etc.) and 'when' with a clear 'Use when implementing infrastructure as code with Terraform' trigger clause at the start, plus additional 'Invoke for...' guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Terraform', 'infrastructure as code', 'AWS', 'Azure', 'GCP', 'module', 'state management', 'import existing resources', 'backend', 'multi-environment'. These cover common variations of how users would phrase Terraform-related requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Terraform specifically, with distinct triggers like 'Terraform', 'state management', 'module versioning', and cloud provider names in the IaC context. Unlikely to conflict with general cloud or coding skills due to the Terraform-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured Terraform skill with strong workflow clarity, excellent progressive disclosure via the reference table, and fully actionable code examples. Its main weakness is moderate verbosity—the persona description, some constraint items that restate common knowledge, and a few explanatory phrases could be trimmed to improve token efficiency. Overall it's a high-quality skill that would guide Claude effectively through Terraform workflows.
Suggestions
Remove the persona description line ('Senior Terraform engineer specializing in...') as it adds no actionable value.
Trim the MUST DO / MUST NOT DO lists to only include non-obvious constraints; items like 'Run terraform fmt and terraform validate' are already in the workflow and don't need repetition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening sentence describing the persona ('Senior Terraform engineer specializing in...') is unnecessary filler Claude doesn't need. The constraints section restates things that are well-known Terraform best practices. However, the code examples and workflow are reasonably tight without excessive explanation. | 2 / 3 |
Actionability | Provides fully executable HCL code examples for module structure, remote backend configuration, and provider version pinning. Commands are specific (terraform fmt, terraform validate, tflint, terraform plan -out=tfplan). The error recovery section gives concrete remediation steps with actual commands. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced with numbered steps, explicit validation checkpoints at step 5 with a retry loop ('fix and re-run until all checks pass'), and a dedicated error recovery section covering state drift, auth errors, and dependency issues. The feedback loop ('After any fix, return to step 5') is explicit and well-structured. | 3 / 3 |
Progressive Disclosure | The reference guide table provides clear one-level-deep references to five separate files with explicit 'Load When' conditions, keeping the main skill as an overview. Content is well-split between the overview (workflow, constraints, examples) and detailed references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- Reviewed
Table of Contents
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.