CtrlK
BlogDocsLog inGet started
Tessl Logo

terraform-skill

Use when writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops - diagnoses failure mode (identity churn, secrets, blast radius, CI drift, state corruption) with version-aware guards.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-architected skill body: dense and actionable with strong workflows, validation gates for destructive operations, and exemplary progressive disclosure backed by verified reference anchors. The only minor weakness is some summary content that duplicates referenced detail.

DimensionReasoningScore

Conciseness

Mostly lean and table-driven with no padding of concepts Claude already knows, though a few summary sections (Core Principles, Naming/Block Ordering summaries) restate detail already available in the referenced files and could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: concrete commands ('fmt -check', 'validate', 'plan -out', 'trivy config .', 'checkov -d .'), copy-paste HCL snippets, and decision matrices that cover the common cases.

5 / 5

Workflow Clarity

A clear 7-step workflow with explicit validation checkpoints (step 6 'Validate before finalizing', step 7 'Emit the Response Contract') and a hard gate for destructive ops (plan -destroy and explicit confirmation before destroy).

5 / 5

Progressive Disclosure

Clear overview with well-signaled, one-level-deep references; all anchor links verified to resolve in the real bundle files; content is appropriately split across eight reference files with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%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.

A highly specific, well-triggered description that names concrete actions, enumerates failure modes, uses third-person voice, and includes an explicit 'Use when' clause. Minor gap is the absence of synonyms/file extensions like HCL and .tf.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('writing, reviewing, or debugging Terraform/OpenTofu modules, tests, CI, scans, or state ops') plus specific failure modes ('identity churn, secrets, blast radius, CI drift, state corruption'), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('diagnoses failure mode ... with version-aware guards') and when (an explicit 'Use when writing, reviewing, or debugging ...' trigger clause) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural terms users would say ('Terraform', 'OpenTofu', 'modules, tests, CI, scans, state ops') but missing common synonyms and file extensions like 'HCL', '.tf', or 'IaC'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Terraform/OpenTofu failure-mode diagnosis with version-aware guards) with distinct, domain-specific triggers and minimal overlap risk with other 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
antonbabenko/terraform-skill
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.