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.
95
92%
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 an excellent skill description that follows best practices. It uses third person voice, provides specific concrete actions, includes highly distinctive file extensions and terminology as trigger terms, and has a comprehensive 'Use when' clause covering multiple scenarios. The description effectively balances being comprehensive while remaining focused on a clear niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple 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 | Includes excellent natural keywords users would say: 'Terraform Stacks', '.tfcomponent.hcl', '.tfdeploy.hcl', 'stack components', 'deployments', 'local modules', 'public registry', 'private registry', 'multi-region', 'multi-environment'. File extensions are particularly useful triggers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific file extensions (.tfcomponent.hcl, .tfdeploy.hcl) and 'Terraform Stacks' terminology that clearly differentiates from general Terraform skills or other IaC tools. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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, highly actionable skill for Terraform Stacks with excellent progressive disclosure and clear workflows. The main weakness is some verbosity in the Core Concepts section and occasional explanatory text that assumes less of Claude's baseline knowledge than necessary. The code examples are comprehensive and executable, and the reference structure is exemplary.
Suggestions
Trim or remove the 'Core Concepts' section - the definitions of Stack, Component, and Deployment are self-evident from the examples and add ~100 tokens of unnecessary context
Remove explanatory phrases like 'This approach:' followed by bullet lists explaining benefits of OIDC - Claude understands authentication patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanations (e.g., explaining what a Stack is, what a Component is) that Claude would already understand. Some sections like 'Core Concepts' could be trimmed since the examples make the concepts clear. | 2 / 3 |
Actionability | Provides fully executable HCL code examples throughout, with copy-paste ready configurations for providers, components, deployments, and CLI commands. Examples are complete and specific with real syntax. | 3 / 3 |
Workflow Clarity | Clear sequenced workflows with explicit validation steps (init -> validate -> upload -> monitor -> approve). The deployment workflow section clearly numbers steps and includes validation commands. Destruction workflow explicitly states the required sequence. | 3 / 3 |
Progressive Disclosure | Excellent structure with a comprehensive overview and well-signaled one-level-deep references to detailed documentation (component-blocks.md, deployment-blocks.md, examples.md, api-monitoring.md, etc.). Content is appropriately split between main skill and reference files. | 3 / 3 |
Total | 11 / 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.
9f2ede9
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.