Name: terraform-skill
Rating: 53.6 (1 reviews)
Author: administrakt0r

Blog Docs Log inGet started

terraform-skill

Terraform infrastructure as code best practices

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/terraform-skill/SKILL.md

The canonical home for this skill is terraform-skill in administrakt0r/AI-Agents-Safe-Coding-Skills

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 content is highly actionable and well-structured with executable examples and clear multi-step workflows, but its progressive-disclosure references point to guide files that do not exist in the bundle, weakening navigation.

Suggestions

Provide the referenced guide files (Testing Frameworks, Module Patterns, CI/CD Workflows, Security & Compliance, Quick Reference, Code Patterns) under references/ so the signaled navigation resolves.

Add an explicit validate→fix→retry loop for destructive/state-affecting operations (e.g., 'terraform plan' review before apply, and re-run validate after fixes).

Tighten the framing prose ('Why this matters', 'Key principle') to reduce minor verbosity without losing the actionable examples.

Dimension	Reasoning	Score
Conciseness	The body is dense and actionable (tables, HCL, commands) and assumes Claude's Terraform knowledge rather than re-explaining basics, with only minor framings ('Key principle...', 'Why this matters') that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides copy-paste-ready HCL blocks and concrete commands (e.g. 'trivy config .', 'terraform init -upgrade', 'checkov -d .') across the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	Multi-step sequences are clearly listed (CI/CD validate→test→plan→apply; version init→upgrade→plan) with most checkpoints present, but destructive/infra-deletion operations lack an explicit validate→fix→retry feedback loop, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	The body is well organized and repeatedly signals one-level-deep reference guides, but the referenced bundle files (references/ etc.) are not present, so the signaled navigation points to missing material — better than buried references but with a real broken-structure gap.	3 / 5
	Total	16 / 20 Passed

Description

43%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 identifies a clear, distinctive niche but is too generic: it states no concrete capabilities and lacks any explicit 'Use when' trigger guidance, leaving Claude without activation cues.

Suggestions

Replace 'best practices' with concrete actions, e.g. 'Write, validate, test, and refactor Terraform/OpenTofu configurations and modules'.

Add an explicit trigger clause: 'Use when creating or reviewing Terraform/OpenTofu configs, modules, testing, or CI/CD for IaC'.

Include natural synonyms users say — 'Terraform', 'OpenTofu', 'HCL', '.tf', 'IaC' — to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Terraform infrastructure as code best practices' names the domain clearly but provides no concrete actions (e.g., 'validate', 'test', 'provision'), matching the 'names domain, actions minimal/generic' anchor rather than the vague-only anchor (1) or the concrete-actions anchor (3).	2 / 5
Completeness	It gives only a vague 'what' ('best practices') and entirely lacks a 'when'/'Use when' trigger clause, matching the 'vague what and no when' anchor; the missing trigger guidance would cap completeness at 3 even if the what were clearer.	2 / 5
Trigger Term Quality	It includes relevant natural terms ('Terraform', 'infrastructure as code') but omits common synonyms and extensions users would say ('OpenTofu', '.tf', 'HCL', 'IaC'), fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Terraform infrastructure as code' carves out a clear niche with distinct triggers and minimal overlap risk with unrelated skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	12 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (515 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/terraform-skill/SKILL.md
Commit: 57c135b

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.