terraform-style-check
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
76
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/terraform-style-check/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 (Terraform HCL). Its main weakness is a lack of specific concrete actions beyond 'generate code' and limited trigger term coverage that misses common user phrasings like '.tf files' or 'infrastructure as code'.
Suggestions
Add specific concrete actions such as 'create resource blocks, define variables and outputs, configure providers, structure modules' to improve specificity.
Expand trigger terms to include common variations like '.tf files', 'infrastructure as code', 'IaC', 'terraform modules', 'terraform providers' to improve discoverability.
| 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, actionable Terraform style guide with excellent concrete examples and good organization. Its main weaknesses are verbosity (includes some content Claude already knows, like version constraint operators and basic security hygiene) and the lack of explicit validation feedback loops in the workflow. Splitting some of the detailed pattern examples into separate reference files would improve token efficiency.
Suggestions
Remove content Claude already knows: version constraint operator definitions, basic security advice like 'never hardcode credentials', and version control basics (.gitignore patterns).
Add an explicit validation feedback loop to the code generation workflow: after generating code, run `terraform fmt` and `terraform validate`, fix any issues, and re-validate before considering the task complete.
Consider splitting detailed pattern examples (secure S3 bucket, dynamic resource creation) into a separate PATTERNS.md file referenced from the main skill.
| 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 standard Terraform knowledge, security best practices like 'never hardcode credentials' are obvious). The version control section (what to commit/not commit) is also basic knowledge. | 2 / 3 |
Actionability | Excellent actionability with fully executable HCL code examples throughout, concrete file organization tables, specific naming conventions with good/bad comparisons, and copy-paste ready configurations for common patterns like secure S3 buckets, VPCs, and provider setup. | 3 / 3 |
Workflow Clarity | The code generation strategy provides a clear 5-step sequence, and the validation tools section mentions `terraform fmt` and `terraform validate`, but there's no explicit feedback loop (validate -> fix -> retry) for the code generation workflow. The checklist at the end is helpful but is presented as a review artifact rather than an integrated validation step in the workflow. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a logical flow, but it's a monolithic document that could benefit from splitting detailed sections (e.g., security examples, dynamic resource creation patterns) into separate reference files. The external reference link to HashiCorp docs is good but the inline content is quite dense. | 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
- warpdotdev/oz-skills
- Commit
6c08c49
- 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.