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.
88
82%
Does it follow best practices?
Impact
100%
1.66xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
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 Stacks, lists concrete actions, includes natural trigger terms with specific file extensions, and provides explicit 'Use when' guidance. It is well-differentiated from general Terraform or IaC skills through its focus on Stacks-specific concepts and file types. The description is concise yet comprehensive, covering the key scenarios without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating, modifying, validating Stack configurations, working with stack components and deployments from various sources (local modules, public registry, private registry), managing multi-region/multi-environment infrastructure, and troubleshooting syntax and structure. | 3 / 3 |
Completeness | Clearly answers both 'what' (comprehensive guide for working with Terraform Stacks) and 'when' with an explicit 'Use when...' clause listing four distinct trigger scenarios: creating/modifying/validating configs, working with sources, managing multi-region/environment infra, and troubleshooting. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'Terraform Stacks', '.tfcomponent.hcl', '.tfdeploy.hcl', 'stack components', 'deployments', 'multi-region', 'multi-environment', 'public registry', 'private registry', 'Terraform Stacks syntax'. These cover file extensions, concepts, and common user language well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around HashiCorp Terraform Stacks specifically, including unique file extensions (.tfcomponent.hcl, .tfdeploy.hcl) that distinguish it from general Terraform skills or other IaC tools. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable Terraform Stacks skill with excellent code examples covering all major configuration blocks and CLI commands. Its main weaknesses are moderate verbosity (some conceptual explanations and obvious best practices that Claude doesn't need), and a workflow section that lacks explicit validation feedback loops for destructive operations. The progressive disclosure structure is reasonable with clear references but the main file carries too much inline detail.
Suggestions
Trim the Core Concepts section to a brief glossary or remove it entirely—Claude understands these abstractions from context and the code examples.
Add explicit validation feedback loops to the deployment workflow: e.g., 'If validate fails → fix syntax → re-validate before uploading' and 'After upload → check configuration watch → if errors, fix and re-upload'.
Move detailed block references (store blocks, deployment auto-approve, deployment groups) entirely to the referenced files to reduce the main SKILL.md length and improve the overview-to-detail ratio.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some unnecessary explanations (e.g., 'Terraform Stacks simplify infrastructure provisioning and management at scale' opening paragraph, explaining what components and deployments are conceptually). Some sections like Best Practices contain obvious advice ('Use descriptive names'). However, most content is substantive and the code examples are lean. | 2 / 3 |
Actionability | The skill provides fully executable HCL code blocks for every major concept (variables, providers, components, deployments, outputs), concrete CLI commands with proper syntax, and specific file structure examples. Code is copy-paste ready with realistic values and patterns. | 3 / 3 |
Workflow Clarity | The CLI deployment workflow is sequenced (init → validate → upload → monitor → approve) but lacks explicit validation checkpoints and error recovery loops. For a destructive operation like deployment destruction, the steps are listed but without validation gates. The 'validate' step exists but isn't integrated into a feedback loop with clear 'if errors, then fix and retry' guidance. | 2 / 3 |
Progressive Disclosure | The skill references six files in a `references/` directory for detailed documentation, which is good structure. However, no bundle files were provided, so we cannot verify these references exist. The main SKILL.md itself is quite long (~350+ lines) with substantial inline content that could be offloaded to reference files (e.g., the full CLI command listing, store blocks, deployment auto-approve details). The overview-to-detail ratio is weighted too heavily toward inline detail. | 2 / 3 |
Total | 9 / 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.
43ca9b0
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.