terraform-engineer
tessl i github:jeffallan/claude-skills --skill terraform-engineerUse when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development, state management, provider configuration, multi-environment workflows, infrastructure testing.
Review Score
67%
Validation Score
13/16
Implementation Score
42%
Activation Score
90%
Generated
Validation
Total
13/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
Implementation
Suggestions 4
Score
42%Overall Assessment
This skill has strong organizational structure with excellent progressive disclosure through its reference table, but critically lacks actionable code examples. The content describes what to do conceptually without providing executable Terraform snippets, making it more of a checklist than a practical guide. The workflow needs explicit validation steps for infrastructure operations.
Suggestions
- Add executable Terraform code examples showing module structure, backend configuration, and provider setup - at minimum one complete, copy-paste ready example
- Include explicit validation workflow: 'terraform plan -out=plan.tfplan' -> review output -> 'terraform apply plan.tfplan' with error handling guidance
- Remove the role-playing framing ('You are a senior DevOps engineer...') and 'Knowledge Reference' section listing concepts Claude already knows
- Add a concrete example in the Output Templates section showing actual HCL code structure rather than just describing what files to create
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill includes some unnecessary framing ('You are a senior DevOps engineer with 10+ years...') and the 'Knowledge Reference' section lists concepts Claude already knows. However, the constraints and workflow sections are reasonably efficient. |
Actionability | 1/3 | The skill lacks any concrete, executable code examples. No actual Terraform HCL snippets, no specific commands beyond mentioning 'terraform fmt and validate', and the 'Output Templates' section describes what to provide rather than showing examples. |
Workflow Clarity | 2/3 | The 5-step core workflow provides a sequence but lacks validation checkpoints and feedback loops. For infrastructure operations that can be destructive, there's no explicit 'plan -> review -> apply' validation cycle or error recovery guidance. |
Progressive Disclosure | 3/3 | Excellent use of a reference table with clear topics, file paths, and 'Load When' guidance. The skill serves as a concise overview pointing to one-level-deep references for detailed content. |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a solid skill description with excellent trigger terms and clear when/what guidance. The main weakness is that the capabilities listed are somewhat categorical (e.g., 'state management') rather than concrete actions (e.g., 'migrate state between backends, import existing resources'). The description effectively distinguishes itself through Terraform-specific terminology.
Suggestions
- Make capabilities more concrete by expanding categories into specific actions, e.g., 'state migration, remote backend setup, resource importing' instead of just 'state management'.
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (Terraform, IaC) and lists several actions (module development, state management, provider configuration, multi-environment workflows, infrastructure testing), but these are somewhat high-level categories rather than concrete specific actions like 'create VPC modules' or 'migrate state between backends'. |
Completeness | 3/3 | Explicitly answers both what (module development, state management, provider configuration, multi-environment workflows, infrastructure testing) and when ('Use when implementing infrastructure as code with Terraform', 'Invoke for...'). Has clear trigger guidance at the start. |
Trigger Term Quality | 3/3 | Includes strong natural keywords users would say: 'Terraform', 'infrastructure as code', 'AWS', 'Azure', 'GCP', 'module', 'state management', 'provider configuration'. These cover common variations and terms users naturally use when working with Terraform. |
Distinctiveness Conflict Risk | 3/3 | Clearly scoped to Terraform specifically with explicit cloud provider mentions (AWS, Azure, GCP). The combination of 'Terraform' + specific IaC concepts creates a distinct niche unlikely to conflict with general cloud skills or other IaC tools like Pulumi or CloudFormation. |