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.
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 a strong skill description that clearly defines its scope around HashiCorp Terraform Stacks, lists concrete actions, includes an explicit 'Use when...' clause with multiple trigger scenarios, and uses distinctive terminology including specific file extensions. It follows third-person voice and provides enough detail for Claude to confidently select this skill when relevant.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: creating, modifying, validating Stack configurations, working with components and deployments from various sources, 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 multiple trigger scenarios including creating/modifying/validating configurations, working with sources, managing infrastructure, and troubleshooting. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Terraform Stacks', '.tfcomponent.hcl', '.tfdeploy.hcl', 'stack components', 'deployments', 'multi-region', 'multi-environment', 'public registry', 'private registry', and 'troubleshooting'. These cover a wide range of terms a user working with Terraform Stacks would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets the specific niche of HashiCorp Terraform Stacks with unique file extensions (.tfcomponent.hcl, .tfdeploy.hcl) and stack-specific concepts. Unlikely to conflict with general Terraform skills or other IaC tools. | 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 strong, well-structured skill that provides comprehensive, actionable guidance for Terraform Stacks. The content excels at progressive disclosure and workflow clarity, with concrete code examples throughout. The main area for improvement is trimming some conceptual explanations (Core Concepts section, some inline descriptions) that Claude could infer from the code examples and configuration syntax.
Suggestions
Trim or remove the 'Core Concepts' section — the definitions of Stack, Component, and Deployment are self-evident from the configuration examples that follow and consume tokens without adding actionable value.
Remove filler phrases like 'This approach:' bullet lists explaining why OIDC is good — Claude already understands security best practices and the bullet points are descriptive rather than instructive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary explanations (e.g., explaining what a Stack is conceptually, what components and deployments are at a high level). Some sections like 'Core Concepts' could be trimmed since Claude can infer these from the code examples. However, most content is domain-specific configuration syntax that Claude wouldn't inherently know. | 2 / 3 |
Actionability | The skill provides fully executable HCL code blocks for every configuration type, concrete CLI commands with exact syntax, and specific file structure examples. Code examples are copy-paste ready with realistic values and cover all major use cases including providers, components, deployments, identity tokens, and outputs. | 3 / 3 |
Workflow Clarity | The deployment workflow is clearly sequenced with numbered steps (init → validate → upload → monitor → approve). The document includes validation checkpoints (terraform stacks validate before upload), destruction workflow with explicit steps (set destroy=true → upload → approve → remove block), and the CLI section clearly notes that there are no plan/apply commands, preventing a common mistake. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to detailed documentation (component-blocks.md, deployment-blocks.md, linked-stacks.md, examples.md, api-monitoring.md, troubleshooting.md). Each reference is contextually placed near the relevant section and also collected in a final References section. | 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.
- Repository
- hashicorp/agent-skills
- Commit
a4e097d
- 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.