terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
80
70%
Does it follow best practices?
Impact
97%
1.19xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./terraform/code-generation/skills/terraform-style-guide/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is functional with a clear 'Use when' clause and good distinctiveness for Terraform-specific tasks. However, it lacks specificity in the concrete actions it performs (e.g., module creation, variable definitions, resource blocks) and could benefit from additional trigger terms that users naturally use when working with Terraform.
Suggestions
Add specific concrete actions like 'create resource blocks, define variables and outputs, configure providers, structure modules' to improve specificity.
Include additional natural trigger terms such as '.tf files', 'infrastructure as code', 'IaC', 'terraform modules', 'terraform providers' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform HCL) and mentions style conventions and best practices, but doesn't list specific concrete actions like 'create modules, define variables, configure providers, write resource blocks'. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate Terraform HCL code following HashiCorp's style conventions and best practices) and 'when' (Use when writing, reviewing, or generating Terraform configurations) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes good terms like 'Terraform', 'HCL', and 'Terraform configurations', but misses common variations users might say such as '.tf files', 'infrastructure as code', 'IaC', 'terraform modules', 'terraform plan', or 'HashiCorp'. | 2 / 3 |
Distinctiveness Conflict Risk | Terraform HCL is a clear niche with distinct triggers. It's unlikely to conflict with other skills since it specifically targets Terraform configurations and HashiCorp conventions. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable Terraform style guide with excellent concrete examples and good/bad comparisons. Its main weaknesses are moderate verbosity (explaining things Claude likely knows, like version constraint operators and basic gitignore patterns), a missing validation feedback loop in the workflow, and a broken reference to SECURITY.md with no supporting bundle. The content would benefit from trimming known concepts and adding an explicit validate-fix cycle.
Suggestions
Add an explicit feedback loop to the workflow: after `terraform validate`, include steps for handling failures (review errors, fix, re-validate) before proceeding.
Remove or significantly trim sections Claude already knows: version constraint operator definitions, basic .gitignore guidance, and explanations of what provider configuration does.
Either include the referenced SECURITY.md as a bundle file or inline the key security points to avoid a broken reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code examples, but includes some unnecessary content Claude already knows (version constraint operator explanations, basic .gitignore guidance, what files to commit). The version pinning section is partially duplicated. Some sections like Provider Configuration add moderate value but could be trimmed. | 2 / 3 |
Actionability | The skill provides fully executable HCL code examples throughout, with concrete good/bad comparisons, specific file organization, and copy-paste ready configurations. The code review checklist and validation commands are directly actionable. | 3 / 3 |
Workflow Clarity | The 'Code Generation Strategy' provides a clear sequence for generating Terraform code, and the validation tools section mentions fmt/validate. However, there's no explicit feedback loop for validation failures (e.g., 'if validate fails, fix and re-run'). For a code generation skill that could produce invalid configurations, the lack of a validate-fix-retry loop is a gap. | 2 / 3 |
Progressive Disclosure | The skill references SECURITY.md for security best practices, which is good progressive disclosure. However, no bundle files are provided, so that reference is broken. The skill is also quite long (~200+ lines) and some sections (version constraint operators, provider configuration, version control guidance) could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 9 / 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
- hashicorp/agent-skills
- Commit
339a113
- 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.