terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
91
70%
Does it follow best practices?
Impact
93%
1.40xAverage score across 10 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 well-structured with a clear 'Use when...' clause and targets a distinct domain. Its main weakness is a lack of specific concrete actions beyond the general 'generate code' and limited trigger term coverage. Adding more specific capabilities and natural keyword variations would strengthen it.
Suggestions
Add specific concrete actions such as 'create resource blocks, define variables and outputs, configure providers, structure modules' to improve specificity.
Include additional trigger terms users might naturally use, such as '.tf files', 'infrastructure as code', 'IaC', 'terraform modules', 'terraform providers'.
| 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; 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, comprehensive Terraform style guide with excellent actionability through concrete, executable HCL examples and good/bad comparisons. Its main weaknesses are length (could be more concise by trimming well-known concepts and splitting advanced topics into referenced files) and the lack of an explicit validation feedback loop in the workflow. The content would benefit from being restructured as a concise overview with pointers to detailed reference files.
Suggestions
Trim sections covering knowledge Claude already has (version constraint operators, basic security principles like 'never hardcode credentials') to improve conciseness.
Add an explicit validate-fix-retry feedback loop to the Code Generation Strategy, e.g., 'After generating, run terraform fmt and terraform validate; if errors, fix and re-validate before presenting.'
Split detailed sections (security examples, provider configuration, version pinning) into separate reference files and link to them from the main skill to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good use of tables and code examples, but it's quite long (~250 lines) and includes some content Claude already knows (e.g., version constraint operators are well-documented knowledge, security best practices like 'never hardcode credentials' are obvious). Some sections like Provider Configuration and Version Pinning could be trimmed. | 2 / 3 |
Actionability | Excellent actionability throughout — every section includes fully executable HCL code examples that are copy-paste ready. Good/bad comparisons for naming conventions and dynamic resource creation provide concrete, specific guidance. The code review checklist and bash commands are directly usable. | 3 / 3 |
Workflow Clarity | The 'Code Generation Strategy' provides a clear 5-step sequence, and the code review checklist is useful. However, there's no explicit validation feedback loop — the validation tools section just lists commands without integrating them into the generation workflow (e.g., 'run fmt, check output, fix if needed'). For a code generation skill, a validate-fix-retry loop would strengthen this. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical flow, but it's monolithic — everything is in one file with no references to supplementary materials. The security examples, provider configuration details, and version pinning 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
de4323a
- 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.