CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.58x
Quality

93%

Does it follow best practices?

Impact

98%

1.58x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, actionable, and well-structured with real progressive disclosure into six existing reference files. Its main weakness is workflow clarity: the deployment workflow and the destructive destroy path lack explicit validation checkpoints and feedback loops.

Suggestions

Make 'terraform stacks validate' an explicit gated step in the deployment workflow ('validate -> only then upload configuration') with a fix-and-revalidate loop on failure.

Add a validation/retry checkpoint to the deployment-destruction sequence (set destroy=true, upload, verify the destroy run plan, then remove the block) since it is destructive.

Add a brief preflight checklist before 'terraform stacks configuration upload' so Claude confirms validation passed and the lock file is committed.

DimensionReasoningScore

Conciseness

Lean, domain-specific prose that assumes competence — it documents Stack-specific blocks and CLI behavior rather than explaining what Terraform or HCL is, and every section earns its place.

3 / 3

Actionability

Provides concrete, executable HCL blocks and copy-paste-ready bash CLI commands throughout (e.g. the component, deployment, and identity_token blocks and the 'terraform stacks' command list), not pseudocode.

3 / 3

Workflow Clarity

The deployment workflow is numbered and sequenced, but it lacks explicit validation checkpoints: 'terraform stacks validate' is listed separately rather than as a gate before 'configuration upload', and the destructive deployment-destruction path has no validate->fix->retry feedback loop.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview that signals one-level-deep references to six real bundle files (component-blocks.md, deployment-blocks.md, linked-stacks.md, examples.md, api-monitoring.md, troubleshooting.md), all of which exist, with no nested-reference chains.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, trigger-rich, and complete, clearly stating both what the skill does and when to invoke it in third-person voice. It is highly distinct and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person voice: 'creating, modifying, or validating Terraform Stack configurations', 'managing multi-region or multi-environment infrastructure', and 'troubleshooting Terraform Stacks syntax and structure'.

3 / 3

Completeness

Clearly answers both 'what' (a guide for working with Terraform Stacks) and 'when' via an explicit 'Use when creating, modifying, or validating...' clause, so both halves are explicitly present.

3 / 3

Trigger Term Quality

Strong coverage of natural terms users would say — 'Terraform Stacks', the .tfcomponent.hcl/.tfdeploy.hcl file extensions, 'components and deployments', 'multi-region', and 'troubleshooting' — with no jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

A clear niche tied to Terraform Stacks and its specific file extensions, making it unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
hashicorp/agent-skills
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.