terraform-style-check
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:warpdotdev/oz-skills --skill terraform-style-check82
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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, making it complete and distinctive. However, it could be stronger by listing more specific actions (module creation, resource definitions, variable handling) and including additional trigger terms users commonly use when working with infrastructure as code.
Suggestions
Add specific concrete actions like 'create modules, define resources, configure providers, manage state' to improve specificity
Include additional trigger terms such as 'infrastructure as code', 'IaC', '.tf files', 'terraform modules' to capture more natural user language
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Terraform HCL code) 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 | Terraform/HCL is a distinct niche that wouldn't conflict with general coding skills or other infrastructure tools. The specific mention of HashiCorp conventions further narrows the scope. | 3 / 3 |
Total | 10 / 12 Passed |
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 Terraform style guide with excellent actionability and conciseness. The executable code examples and clear conventions make it immediately useful. The main weaknesses are the lack of integrated validation checkpoints in the workflow and the monolithic structure that could benefit from progressive disclosure to separate reference material.
Suggestions
Integrate validation steps into the Code Generation Strategy section (e.g., 'After step 3, run terraform validate; if errors, fix and re-validate before proceeding')
Consider splitting detailed examples (Secure S3 Bucket, Provider Configuration) into a separate EXAMPLES.md file with clear references from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting conventions and examples without explaining what Terraform is or how HCL works. Every section provides actionable guidance without unnecessary preamble. | 3 / 3 |
Actionability | Provides fully executable HCL code examples throughout, including complete resource definitions, variable declarations, and provider configurations. Examples are copy-paste ready with realistic values. | 3 / 3 |
Workflow Clarity | The code generation strategy provides a clear sequence, but validation steps are mentioned only at the end ('Run before committing') rather than integrated into the workflow. Missing explicit feedback loops for fixing validation errors. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a table of contents via headers, but it's a monolithic document (~250 lines) that could benefit from splitting detailed examples (like the secure S3 bucket) into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
93%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 15 / 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.