terraform-specialist

Expert Terraform/OpenTofu specialist mastering advanced IaC automation, state management, and enterprise infrastructure patterns. Handles complex module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration. Covers migration strategies, security best practices, and modern IaC ecosystems. Use PROACTIVELY for advanced IaC, state management, or infrastructure automation.

Quality

50%

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 ./skills/terraform-specialist/SKILL.md

Quality

Content

25%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 reads like a resume/encyclopedia of Terraform topics rather than actionable skill guidance: it enumerates concepts Claude already knows, provides no executable code or commands, and inlines everything with no external references. It fails the core purpose of a skill body, which is to tell Claude concretely what to do.

Suggestions

Replace the capability enumerations with a lean workflow of concrete, executable steps (e.g., actual `terraform`/`tofu` commands, module skeleton code, backend config snippets).

Add explicit validation checkpoints to the plan/apply workflow (e.g., 'terraform validate', 'terraform plan -out=tfplan', review, then 'terraform apply tfplan') given apply is destructive.

Move the long capability/topic lists into separate reference files under references/ and link to them one level deep, keeping SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The 155-line body is a heavily padded enumeration of capability lists ('Resources, data sources, variables, outputs, locals, expressions', 'Dynamic blocks, for_each loops') that mostly restates knowledge Claude already has, plus redundant sections (Purpose, Knowledge Base, Behavioral Traits) that restate the description.	2 / 5
Actionability	There is no executable code or command anywhere; the Instructions ('Define environments, providers, and security constraints', 'Design modules and choose a remote state backend') and Response Approach are high-level hints missing the specific steps to actually execute.	2 / 5
Workflow Clarity	The Instructions section gives a rough 4-step sequence but steps are poorly defined with no concrete commands, and validation for the destructive plan/apply workflow is largely absent (only a vague 'reviews and policies' mention and a Safety note).	2 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets all absent) and the body is a monolithic inline enumeration of capability lists that clearly belong in separate reference files, with only section headers providing minimal structure.	2 / 5
	Total	8 / 20 Passed

Description

75%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 well-constructed: third-person voice, comprehensive capability coverage, and an explicit trigger clause. It sits comfortably above midpoint on all dimensions but is held back from top scores by buzzword padding and a trigger clause that could enumerate more concrete, natural user phrases.

Suggestions

Replace buzzword padding ('mastering advanced IaC automation', 'enterprise infrastructure patterns') with concrete actions a user would recognize.

Expand the trigger clause with more natural user phrases and file extensions (e.g., 'Use when designing Terraform modules, managing .tf state backends, or setting up GitOps for IaC').

Tighten the description to reduce redundancy between the first sentence and the 'Covers...' sentence.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ('module design, multi-cloud deployments, GitOps workflows, policy as code, and CI/CD integration', 'migration strategies, security best practices'), but these are domains rather than ultra-concrete actions and are padded with buzzwords ('mastering advanced IaC automation', 'enterprise infrastructure patterns').	4 / 5
Completeness	Clearly answers 'what' (handles module design, multi-cloud, GitOps, policy as code, CI/CD, migration, security) and 'when' ('Use PROACTIVELY for advanced IaC, state management, or infrastructure automation'), but the 'when' could be more explicit and varied.	4 / 5
Trigger Term Quality	Good keyword coverage with natural terms users would say ('Terraform', 'OpenTofu', 'state management', 'GitOps', 'CI/CD', 'infrastructure automation'), but a few natural synonyms/extensions are missing (e.g., 'HCL', '.tf files').	4 / 5
Distinctiveness Conflict Risk	Terraform/OpenTofu specialization is a clear niche with distinct triggers, but the broad 'infrastructure automation' trigger creates minor overlap risk with general DevOps/infra skills.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/terraform-specialist/SKILL.md
Commit: 3eff4af

Reviewed: 15 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.