terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%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 description with excellent trigger term coverage and specificity for the Terraform/OpenTofu domain. The main weakness is structural: it leads with 'Use when...' without first stating what the skill does, making the 'what' implicit rather than explicit. Reordering to state capabilities first, then triggers, would improve completeness.
Suggestions
Add an explicit capability statement before the 'Use when...' clause, e.g., 'Provides guidance for Terraform and OpenTofu infrastructure-as-code development, testing, and operations.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions'. | 3 / 3 |
Completeness | The description starts with 'Use when...' which addresses the 'when' clearly, but the 'what does this do' is only implied through the list of activities. There's no explicit statement of the skill's core capability before the trigger guidance. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Terraform', 'OpenTofu', 'modules', 'tests', 'Terratest', 'CI/CD pipelines', 'state issues', 'trivy', 'checkov', 'infrastructure-as-code'. These are terms practitioners naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct triggers specific to Terraform/OpenTofu ecosystem. The mention of specific tools (Terratest, trivy, checkov) and domain-specific concepts (state issues, native test framework) makes it highly distinguishable from general DevOps or cloud skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%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, comprehensive Terraform skill that excels in actionability and progressive disclosure. The decision matrices, concrete code examples, and clear references to detailed guides make it highly usable. Minor verbosity in some explanatory sections (naming conventions, basic concepts) could be trimmed to improve token efficiency.
Suggestions
Trim the 'Naming Conventions' section - Claude understands descriptive naming; focus only on the 'this' singleton pattern which is Terraform-specific
Remove explanatory text like 'PDF (Portable Document Format)' equivalents - e.g., 'Resource Module: Single logical group of connected resources' could just show the table without the 'When to Use' column header explanation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient but includes some unnecessary explanations (e.g., explaining what singleton resources are, basic file naming conventions Claude already knows). The tables and decision matrices add value, but some sections could be tightened. | 2 / 3 |
Actionability | Excellent actionability with executable code examples throughout, specific commands (trivy, checkov, terraform init -upgrade), concrete patterns with ✅ DO vs ❌ DON'T comparisons, and copy-paste ready HCL blocks. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints (CI/CD stages, update workflow with plan step, testing pyramid). The decision matrices provide clear sequencing for choosing approaches, and the module development section has clear structure. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to detailed guides (testing-frameworks.md, module-patterns.md, ci-cd-workflows.md, etc.). Navigation is clear with descriptive links. | 3 / 3 |
Total | 11 / 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 (517 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- antonbabenko/terraform-skill
- Commit
5a68694
- 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.