terraform-stacks
Comprehensive guide for working with HashiCorp Terraform Stacks. Use when creating, modifying, or validating Terraform Stack configurations (.tfcomponent.hcl, .tfdeploy.hcl files), working with stack components and deployments from local modules, public registry, or private registry sources, managing multi-region or multi-environment infrastructure, or troubleshooting Terraform Stacks syntax and structure.
Overall
score
86%
Does it follow best practices?
Evaluation — 96%
↑ 2.04xAgent success when using this skill
Validation for skill structure
Install with Tessl CLI
npx tessl i github:hashicorp/agent-skills --skill terraform-stacksActivation
100%This is an excellent skill description that clearly defines its scope around HashiCorp Terraform Stacks with specific file types, actions, and use cases. It uses proper third-person voice, includes an explicit 'Use when' clause with multiple trigger scenarios, and provides enough technical specificity (file extensions, registry sources) to distinguish it from general Terraform skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating, modifying, or validating Terraform Stack configurations', 'working with stack components and deployments', 'managing multi-region or multi-environment infrastructure', and 'troubleshooting Terraform Stacks syntax and structure'. | 3 / 3 |
Completeness | Clearly answers both what ('Comprehensive guide for working with HashiCorp Terraform Stacks') and when with explicit 'Use when' clause covering four distinct trigger scenarios including file types, sources, infrastructure patterns, and troubleshooting. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Terraform Stacks', '.tfcomponent.hcl', '.tfdeploy.hcl', 'stack components', 'deployments', 'local modules', 'public registry', 'private registry', 'multi-region', 'multi-environment infrastructure'. Includes both file extensions and conceptual terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche targeting specifically 'Terraform Stacks' (not general Terraform), unique file extensions (.tfcomponent.hcl, .tfdeploy.hcl), and specific concepts like stack components and deployments that distinguish it from general Terraform or IaC skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%This is a comprehensive and actionable Terraform Stacks reference with excellent code examples and good organization. The main weaknesses are some unnecessary conceptual explanations that Claude doesn't need, and a lack of explicit validation workflows with feedback loops for multi-step operations like deployment creation and destruction.
Suggestions
Trim the 'Core Concepts' section significantly - Claude understands infrastructure concepts; focus on Stacks-specific syntax differences only
Add explicit validation workflows with feedback loops, e.g., 'Run terraform stacks validate -> if errors, check X -> fix -> re-validate -> only proceed when valid'
Remove explanatory phrases like 'Works exactly as in traditional Terraform' - just show the syntax
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally efficient but includes some explanatory text Claude would already know (e.g., explaining what a Stack is, what components are). The examples are good but some sections like 'Core Concepts' could be trimmed since Claude understands infrastructure concepts. | 2 / 3 |
Actionability | Excellent executable code examples throughout with complete HCL configurations that are copy-paste ready. CLI commands are specific and concrete. The file structure, block syntax, and patterns are all immediately usable. | 3 / 3 |
Workflow Clarity | While the content covers many operations, it lacks explicit validation checkpoints and feedback loops. The 'Initialize and Validate' section lists commands but doesn't integrate validation into a clear workflow with error recovery steps. The 'Destroying a Deployment' section is a good example of sequenced steps but most other multi-step processes lack this clarity. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, a recommended file organization upfront, and appropriate references to external files (references/component-blocks.md, etc.) at the end. Content is appropriately split between quick-reference patterns and detailed block specifications. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
88%Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (572 lines); consider splitting into references/ and linking | 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.