terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution.
84
88%
Does it follow best practices?
Impact
84%
1.78xAverage score across 10 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that hits all the key criteria. It provides specific concrete actions, uses natural terminology that Terraform users would employ, explicitly states both what the skill does and when to use it, and carves out a distinct niche focused specifically on Terraform testing rather than general Terraform usage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating test files (.tftest.hcl)', 'writing test scenarios with run blocks', 'validating infrastructure behavior with assertions', 'mocking providers and data sources', 'testing module outputs and resource configurations', 'troubleshooting Terraform test syntax and execution'. | 3 / 3 |
Completeness | Clearly answers both what ('Comprehensive guide for writing and running Terraform tests') and when ('Use when creating test files, writing test scenarios, validating infrastructure behavior...') with explicit trigger scenarios listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Terraform tests', '.tftest.hcl', 'run blocks', 'assertions', 'mocking providers', 'data sources', 'module outputs', 'resource configurations'. These are terms Terraform users would naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche focus on Terraform testing specifically. The mention of '.tftest.hcl', 'run blocks', and 'mocking providers' creates a distinct trigger profile that wouldn't conflict with general Terraform skills or other testing frameworks. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured Terraform testing guide with excellent executable examples and clear workflows. However, it suffers from verbosity - the document is excessively long with content that could be condensed or split into separate files. The mock testing section in particular includes extensive commentary that inflates token usage without proportional value.
Suggestions
Split the mock testing section (with its extensive examples and guidelines) into a separate MOCK_TESTING.md file and reference it from the main skill
Move CI/CD integration examples to a separate CI_CD.md file since they are supplementary to the core testing concepts
Condense the 'Key Benefits/Limitations/When to Use' lists in the mock section - Claude can infer most of these from the examples
Remove redundant explanations like 'Mock tests are ideal for:' lists that repeat information already demonstrated in the examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly verbose in places. It includes some unnecessary explanations (e.g., explaining what a PDF is equivalent - explaining basic Terraform concepts Claude knows) and could be significantly condensed. The mock testing section alone is extremely lengthy with extensive commentary that could be trimmed. | 2 / 3 |
Actionability | Excellent actionability with fully executable HCL code examples throughout. Every concept is demonstrated with copy-paste ready code blocks, specific commands for running tests, and complete example test suites covering unit, integration, and mock testing patterns. | 3 / 3 |
Workflow Clarity | Clear sequential workflows with explicit validation steps. The document explains run block execution order, cleanup in reverse order, and includes explicit checkpoints. The test organization section provides clear guidance on structuring unit vs integration tests. | 3 / 3 |
Progressive Disclosure | The content is a monolithic document with everything inline rather than appropriately split across files. While well-organized with clear headers, the 800+ line document would benefit from splitting advanced topics (mock testing, CI/CD integration) into separate referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1670 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.