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.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is highly actionable with executable examples and a clean progressive-disclosure structure backed by real reference files. Its main weakness is conciseness — the Core Concepts primer and some best-practice prose restate knowledge Claude already has — and slightly under-explicit validation checkpoints in the deployment workflow.

Suggestions

Trim or remove the 'Core Concepts' definitions of Stack/Component/Deployment/Stack Language; Claude can infer these, and the File Structure section already conveys the model.

Add explicit validation checkpoints to the deployment workflow (e.g., 'Run `terraform stacks validate` and fix all errors before uploading configuration') to strengthen the feedback loop.

Move the 'Authentication Best Practice' and detailed 'Best Practices' prose into a reference file, keeping only the workload-identity pointer inline.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured with executable HCL/bash blocks, but the opening 'Core Concepts' section explains what a Stack/Component/Deployment is — context Claude can largely infer — and several sections (Authentication Best Practice, Deployment Group, Best Practices) add prose that could be trimmed or moved to references.

3 / 5

Actionability

Provides fully executable, copy-paste-ready HCL blocks for every block type (variable, provider, component, deployment, etc.) plus concrete `terraform stacks` CLI commands covering init, validate, upload, and monitoring workflows.

5 / 5

Workflow Clarity

The deployment workflow is clearly sequenced (init/validate → upload → monitor → approve) with numbered steps and concrete commands, but lacks explicit validation checkpoints after `validate`/`upload` and the destroy sequence is described only as prose rather than an explicit validate-then-destroy feedback loop.

4 / 5

Progressive Disclosure

Clear overview structure with one-level-deep references that all resolve to real files (component-blocks.md, deployment-blocks.md, linked-stacks.md, examples.md, api-monitoring.md, troubleshooting.md), each signaled inline at the relevant section and listed again in a final References block.

5 / 5

Total

17

/

20

Passed

Description

88%Weight 40%Scale 1-5

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 strong: third-person voice, explicit 'Use when' trigger clause, concrete file extensions, and a well-scoped niche. Its only weakness is slight verbosity in the 'when' clause, which lists many scenarios without harming clarity.

DimensionReasoningScore

Specificity

Names the domain (Terraform Stacks) and lists several concrete actions — 'creating, modifying, or validating Terraform Stack configurations', 'working with stack components and deployments', 'managing multi-region or multi-environment infrastructure', 'troubleshooting' — with minor gaps (no mention of the CLI or API monitoring).

4 / 5

Completeness

Explicitly answers 'what' ('Comprehensive guide for working with HashiCorp Terraform Stacks') and 'when' with a concrete 'Use when...' trigger clause enumerating multiple scenarios.

5 / 5

Trigger Term Quality

Strong natural-term coverage including the product name 'Terraform Stacks', file extensions '.tfcomponent.hcl' and '.tfdeploy.hcl', and common variations 'multi-region', 'multi-environment', and 'troubleshooting' that a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche — HashiCorp Terraform Stacks with its proprietary .tfcomponent.hcl/.tfdeploy.hcl extensions — that is unlikely to overlap with or trigger for unrelated skills.

5 / 5

Total

19

/

20

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.