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.
91
86%
Does it follow best practices?
Impact
100%
1.49xAverage score across 3 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 a strong skill description that clearly defines its scope around Terraform testing, provides explicit trigger conditions via a 'Use when...' clause, and includes highly specific technical terms that users would naturally use. It effectively differentiates itself from general Terraform or general testing skills through domain-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing test files, writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, and troubleshooting test syntax and execution. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for writing and running Terraform tests) and 'when' with an explicit 'Use when...' clause listing six specific trigger scenarios. | 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', 'test syntax'. These are terms a Terraform user would naturally use when seeking help with testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Terraform testing specifically, with unique triggers like '.tftest.hcl', 'run blocks', and 'mocking providers' that are unlikely to conflict with general Terraform skills or other testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable Terraform testing skill with excellent progressive disclosure and concrete code examples. Its main weakness is that the inline 'Common Test Patterns' section is overly extensive—many patterns are minor variations that could be moved to the EXAMPLES.md reference file, improving conciseness. The workflow for iterating on test failures could also be more explicit.
Suggestions
Move 4-5 of the simpler test patterns (tags, data sources, plan options, state key sharing) to references/EXAMPLES.md and keep only the most essential patterns inline to improve conciseness.
Add an explicit test-writing workflow: write test → run with -verbose → inspect output → fix assertions → re-run, to strengthen the feedback loop for test development.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient but includes many test patterns that could be consolidated or moved to a reference file. The 'Common Test Patterns' section is extensive (10+ patterns inline) when several are straightforward variations Claude could derive from 2-3 examples. However, it avoids explaining basic Terraform concepts. | 2 / 3 |
Actionability | Every pattern includes complete, executable HCL code blocks with realistic assertions and error messages. The CLI commands section is copy-paste ready, and the run block structure shows all available options with concrete syntax. | 3 / 3 |
Workflow Clarity | The sequential test pattern and cleanup ordering are shown, but there's no explicit validation workflow for writing and running tests (e.g., write test → run → check output → fix assertions → re-run). The troubleshooting table partially compensates but lacks a feedback loop for the test-writing process itself. | 2 / 3 |
Progressive Disclosure | Clear reference file structure with one-level-deep links to MOCK_PROVIDERS.md, CI_CD.md, and EXAMPLES.md. The main file serves as a comprehensive overview with guidance on when to consult each reference file. External documentation links are also provided. | 3 / 3 |
Total | 10 / 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.
b129bb5
Table of Contents
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.