terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
93
83%
Does it follow best practices?
Impact
94%
1.40xAverage score across 10 eval scenarios
Passed
No known issues
Quality
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.
This is a solid description with clear 'what' and 'when' clauses and good distinctiveness for Terraform-specific work. The main weaknesses are moderate specificity (lacks concrete action examples) and limited trigger term coverage (missing common user phrases like 'IaC' or '.tf files').
Suggestions
Add specific concrete actions like 'create modules, define resources, configure providers, set up backends' to improve specificity
Expand trigger terms to include common variations: 'infrastructure as code', 'IaC', '.tf files', 'terraform modules', 'cloud infrastructure'
| 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 resources', 'configure providers', or 'set up state backends'. | 2 / 3 |
Completeness | Clearly answers both what ('Generate Terraform HCL code following HashiCorp's official style conventions and best practices') and when ('Use when writing, reviewing, or generating Terraform configurations') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Terraform', 'HCL', and 'configurations' which are relevant, but misses common variations users might say like 'infrastructure as code', 'IaC', '.tf files', 'terraform modules', 'AWS/Azure/GCP infrastructure'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Terraform HCL with distinct triggers; unlikely to conflict with general coding skills or other infrastructure tools like CloudFormation or Pulumi. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable Terraform style guidance with excellent code examples and clear workflows. The content is well-structured and token-efficient, avoiding unnecessary explanations. The main weakness is that the document is somewhat long and could benefit from splitting advanced topics into separate files for better progressive disclosure.
Suggestions
Consider splitting detailed sections (Security Best Practices, Dynamic Resource Creation, Provider Configuration) into separate reference files linked from the main SKILL.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting information in tables, code blocks, and bullet points without explaining concepts Claude already knows (like what Terraform is or how HCL works). Every section provides actionable guidance without padding. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready HCL code examples throughout. Each concept is demonstrated with concrete, complete code blocks showing both good and bad patterns, with specific commands for validation tools. | 3 / 3 |
Workflow Clarity | Clear 5-step code generation strategy at the top, explicit file organization table, and a comprehensive code review checklist at the end. The workflow for generating Terraform code is unambiguous with validation steps (terraform fmt, terraform validate) clearly specified. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document (~250 lines) that could benefit from splitting detailed sections (like Security Best Practices or Dynamic Resource Creation) into separate reference files. The external HashiCorp reference is appropriately linked. | 2 / 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
- hashicorp/agent-skills
- Commit
9f2ede9
- 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.