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
93%
Does it follow best practices?
Impact
98%
1.58xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Terraform Stack deployment API monitoring script
No watch commands
100%
100%
Token extraction
100%
100%
Authorization header
100%
100%
Content-Type header
100%
71%
Config status polling
100%
87%
Config polling interval
100%
100%
Deployment runs polling
100%
100%
Deployment steps polling
100%
62%
Runs/steps polling interval
0%
100%
Diagnostics step_id param
0%
100%
Artifacts endpoint usage
0%
100%
curl -L for artifacts
0%
100%
Terraform Stack configuration for multi-environment web app
Component file extension
0%
100%
Deployment file extension
100%
100%
Recommended file names
0%
100%
Root-level placement
100%
100%
Terraform version file
0%
100%
Variable type fields
100%
100%
No validation blocks
100%
100%
Ephemeral credentials
0%
100%
Provider alias in header
100%
100%
Provider config block
100%
100%
OIDC auth method
12%
100%
Identity token in deploy file
0%
100%
Deployment groups (not orchestrate)
14%
100%
Output type argument
0%
100%
Module has no provider blocks
100%
100%
Multi-region Stack expansion with component removal
Provider for_each
100%
100%
Regional provider alias in config block
100%
100%
Component for_each
100%
100%
Regional provider reference
100%
100%
Component output reference syntax
100%
100%
removed block present
20%
100%
removed block completeness
0%
100%
No provider blocks in modules
100%
100%
publish_output blocks
20%
100%
ephemeral token variable
100%
100%
No version on local source
100%
100%
regions variable type
100%
100%
bde3ed3
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.