terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
Install with Tessl CLI
npx tessl i github:hashicorp/agent-skills --skill terraform-style-guide92
Quality
79%
Does it follow best practices?
Impact
94%
1.40xAverage score across 10 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./terraform/code-generation/skills/terraform-style-guide/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
79%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, actionable Terraform style guide with excellent code examples and clear conventions. Its main weaknesses are the lack of an integrated validation workflow (generate -> validate -> iterate) and the monolithic structure that could benefit from splitting detailed examples into separate files for better progressive disclosure.
Suggestions
Integrate validation steps into the Code Generation Strategy workflow (e.g., 'After generating code: 1. Run terraform fmt, 2. Run terraform validate, 3. If errors, fix and re-validate, 4. Only commit when validation passes')
Consider splitting detailed examples (secure S3 bucket, provider configuration patterns) into separate reference files and linking from the main skill
| 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 illustrated with concrete, complete code blocks showing both good and bad patterns, with specific commands for validation tools. | 3 / 3 |
Workflow Clarity | The 'Code Generation Strategy' provides a clear sequence, and the checklist at the end is helpful. However, there's no explicit validation/feedback loop for the code generation workflow itself—the validation tools section is separate and doesn't integrate into a 'generate -> validate -> fix -> retry' workflow. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a table of contents via headers, but it's a monolithic document (~300 lines) that could benefit from splitting detailed examples (like the secure S3 bucket) into separate reference files. The external HashiCorp link is good but internal progressive disclosure is limited. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.